Triple
T339630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ogham script |
E6803
|
entity |
| Predicate | associatedCulture |
P1439
|
FINISHED |
| Object | early Irish culture |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: early Irish culture | Statement: [Ogham script, associatedCulture, early Irish culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCulture Context triple: [Ogham script, associatedCulture, early Irish culture]
-
A.
hasAssociatedCulture
chosen
Indicates that an entity is related to, influenced by, or characterized by a particular culture.
-
B.
hasCulturalConcept
Indicates that an entity embodies, includes, or is associated with a particular cultural idea, value, practice, or construct.
-
C.
hasCulturalFeature
Indicates that an entity possesses, includes, or is characterized by a particular cultural element, attribute, or landmark.
-
D.
hasCulturalReference
Indicates that one entity makes reference to, draws from, or is associated with the cultural content, symbols, or traditions represented by another entity.
-
E.
hasCulturalSignificanceFor
Indicates that something holds particular cultural meaning, value, or importance for a specified group or community.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae4fcc08190bd4c2bf0149c8b50 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.