Triple
T17054674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caitríona |
E413787
|
entity |
| Predicate | typicalHeritage |
P1494
|
FINISHED |
| Object | Irish 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: Irish heritage | Statement: [Caitríona, typicalHeritage, Irish heritage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHeritage Context triple: [Caitríona, typicalHeritage, Irish heritage]
-
A.
heritageTradition
Indicates a relationship where a cultural practice, belief, or custom is passed down and maintained as part of a group’s inherited traditions.
-
B.
heritageType
Indicates the classification of an entity’s cultural or natural heritage category or type within a heritage framework.
-
C.
hasHeritage
chosen
Indicates that an entity possesses or is associated with a particular cultural, ethnic, or ancestral background.
-
D.
heritageTransmission
Indicates the passing down of cultural, historical, or familial heritage from one entity or generation to another.
-
E.
retainsHeritageOf
Indicates that one entity preserves, maintains, or keeps alive the cultural, historical, or traditional legacy originating from 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_69d886cde3d481908d4d01ba88ba7eb7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3daa54c808190a6e8333c413f4e26 |
completed | April 18, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:34 a.m.