Triple
T38592176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarab Lord |
E932478
|
entity |
| Predicate | associatedWithDragonflight |
P206566
|
FINISHED |
| Object | Bronze Dragonflight |
E2232126
|
NE 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: Bronze Dragonflight | Statement: [Scarab Lord, associatedWithDragonflight, Bronze Dragonflight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithDragonflight Context triple: [Scarab Lord, associatedWithDragonflight, Bronze Dragonflight]
-
A.
usedDragon
Indicates that one entity employed or controlled a dragon to perform some action or fulfill a purpose.
-
B.
associatedWithSoulsOf
Indicates a relationship in which something is connected, linked, or related specifically to the souls of certain entities.
-
C.
relatedClassInWarcraft
Indicates that two entities are related through a class association within the Warcraft universe, such as sharing, corresponding to, or being mapped between specific Warcraft character classes.
-
D.
dragonriderOf
Indicates that one entity serves as the rider of a particular dragon.
-
E.
associatedWithMonster
Indicates a relationship in which an entity is connected or linked in some notable way to a monster.
- F. None of above. chosen
Provenance (5 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4223a750e8819084de22f574074edf |
completed | June 29, 2026, 7:49 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.