Triple
T11658752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The End |
E277071
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Ender Dragon |
E277072
|
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: Ender Dragon | Statement: [The End, contains, Ender Dragon]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ender Dragon Context triple: [The End, contains, Ender Dragon]
-
A.
Ender Dragon
chosen
The Ender Dragon is the formidable final boss of Minecraft, a massive flying dragon that players must defeat to complete the game’s main storyline.
-
B.
Nebaioth
Nebaioth is a biblical figure known as the firstborn son of Ishmael and ancestor of an Ishmaelite tribe mentioned in the Old Testament.
-
C.
Maldraxxus
Maldraxxus is a war-torn necromantic realm in World of Warcraft: Shadowlands, home to the Necrolords and the military forces that defend the Shadowlands.
-
D.
N’Zoth, the Corruptor
N’Zoth, the Corruptor is an ancient Old God from the Warcraft universe known for his insidious mind control, reality-warping influence, and role as a major antagonist in World of Warcraft.
-
E.
Magmadar
Magmadar is a massive lava hound and one of the early raid bosses in World of Warcraft’s Molten Core instance.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ee882148a08190a1a8c16d8cb7e48a |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 8, 2026, 9:39 p.m.