Triple
T1575462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Celtic nations |
E33639
|
entity |
| Predicate | sharesHeritage |
P1494
|
FINISHED |
| Object | Celtic heritage |
—
|
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: Celtic heritage | Statement: [Celtic nations, sharesHeritage, Celtic heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesHeritage Context triple: [Celtic nations, sharesHeritage, Celtic heritage]
-
A.
hasHeritage
chosen
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
B.
heritageField
Indicates that there is an association between an entity and a specific field, domain, or area related to cultural or historical heritage.
-
C.
retainsHeritageOf
Indicates that one entity preserves, maintains, or keeps alive the cultural, historical, or traditional legacy originating from another entity.
-
D.
heritageFunction
Indicates the role, use, or purpose that a heritage asset or element serves within its cultural, historical, or social context.
-
E.
heritageReference
Indicates that one entity serves as a cultural, historical, or heritage-related reference or source for another entity.
- 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_69a885f27a4c8190a4622252cdf54c00 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907ba63c88190b60c14dec8d1e40f |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:27 p.m.