Triple
T37661671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The End (C418) |
E937730
|
entity |
| Predicate | appearsInGameDimension |
P189171
|
FINISHED |
| Object | The End (Minecraft dimension) |
—
|
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: The End (Minecraft dimension) | Statement: [The End (C418), appearsInGameDimension, The End (Minecraft dimension)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsInGameDimension Context triple: [The End (C418), appearsInGameDimension, The End (Minecraft dimension)]
-
A.
appearsInGameMode
Indicates that an entity is present, available, or featured within a specified game mode.
-
B.
formationDimension
Indicates the dimensional characteristics (such as size, scale, or extent) associated with the formation of something.
-
C.
appearsIn
Indicates that an entity is present, featured, or occurs within a particular context, work, or medium.
-
D.
includesDimension
Indicates that one entity encompasses or contains a particular dimension or measurable aspect as part of its definition or structure.
-
E.
dimensionSpawnsIn
chosen
Indicates that a particular dimension is the location or context in which an entity or object is initially generated or appears.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fec8aef1d8819094c7fd7074038e6b |
completed | May 9, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69fec639876481908efd84a3631a4271 |
completed | May 9, 2026, 5:29 a.m. |
Created at: May 3, 2026, 4:18 p.m.