Triple
T26826188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuatha Dé Danann |
E675381
|
entity |
| Predicate | afterConquestFate |
P32946
|
FINISHED |
| Object | retreated into the sídhe |
—
|
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: retreated into the sídhe | Statement: [Tuatha Dé Danann, afterConquestFate, retreated into the sídhe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterConquestFate Context triple: [Tuatha Dé Danann, afterConquestFate, retreated into the sídhe]
-
A.
afterConquest
Indicates that one event, state, or condition occurs subsequent to and as a result of a conquest having taken place.
-
B.
afterConquestBy
chosen
Indicates that one entity exists in a state, condition, or situation that occurs subsequent to and as a result of being conquered by another entity.
-
C.
postReignFate
Indicates what ultimately happens to a ruler or leader after their reign or period of authority has ended.
-
D.
afterConquestName
Indicates that an entity’s name is the one it is known by after a conquest or successful takeover has occurred.
-
E.
conquestEvent
Indicates an event in which one party gains control over another entity or territory through force or domination.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 4:58 a.m.