Triple
T32998081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tír Chonaill |
E844282
|
entity |
| Predicate | successionCustom |
P71549
|
FINISHED |
| Object | tanistry |
—
|
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: tanistry | Statement: [Tír Chonaill, successionCustom, tanistry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successionCustom Context triple: [Tír Chonaill, successionCustom, tanistry]
-
A.
successionRight
Indicates the legal or customary entitlement of one entity to inherit, assume, or take over the position, property, or role of another.
-
B.
successionAction
Indicates an action or event through which one entity formally replaces or follows another in a sequence or position.
-
C.
successionOrder
Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
-
D.
successionTrigger
Indicates a condition or event that initiates or causes a transfer of position, role, or authority from one entity to another.
-
E.
successionBasis
chosen
Indicates the legal or customary basis on which one entity succeeds or takes over from another in a position, role, or title.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff7595c9bc8190982c6e6e07a0c78f |
completed | May 9, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69ff715432a88190a25670d26614bde2 |
completed | May 9, 2026, 5:39 p.m. |
Created at: May 1, 2026, 1:22 a.m.