Triple
T37553555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragonflight |
E933642
|
entity |
| Predicate | introducesRaceClass |
P141977
|
FINISHED |
| Object | Dracthyr Evoker |
—
|
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: Dracthyr Evoker | Statement: [Dragonflight, introducesRaceClass, Dracthyr Evoker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducesRaceClass Context triple: [Dragonflight, introducesRaceClass, Dracthyr Evoker]
-
A.
introducesRace
chosen
Indicates that one entity presents, initiates, or brings into existence a race, competition, or racial category involving another entity.
-
B.
hasRaceClass
Indicates that an entity participates in or is associated with a particular race classification or category.
-
C.
notableRaceClass
Indicates that there exists a notable race or competition of a particular class or category associated with the subject.
-
D.
appearsAsRacerClass
Indicates that an entity is presented or functions in the role or category of a racer class within a given context.
-
E.
cardRace
Indicates that one entity participates in or is associated with a competitive race involving cards or card-based vehicles relative to 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 3, 2026, 4:17 p.m.