Triple
T26826186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuatha Dé Danann |
E675381
|
entity |
| Predicate | leaderInMyth |
P9987
|
FINISHED |
| Object | Nuada |
—
|
NE NERFINISHED |
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: Nuada | Statement: [Tuatha Dé Danann, leaderInMyth, Nuada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leaderInMyth Context triple: [Tuatha Dé Danann, leaderInMyth, Nuada]
-
A.
mythologicalFigureFeatured
Indicates that a mythological figure is prominently depicted, referenced, or plays a significant role within a given work, context, or medium.
-
B.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
-
C.
leaderFrom
Indicates that an entity serves or has served as a leader originating from, representing, or associated with a specified place or organization.
-
D.
leader2
Indicates that one entity serves as a leader, chief, or primary authority figure in relation to another entity.
-
E.
leaderInSomeContinuities
Indicates that an entity serves as a leader in at least one version, timeline, or continuity of a narrative or setting.
- 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_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 4:58 a.m.