Triple
T37661647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eye of Ender |
E937729
|
entity |
| Predicate | canBeUsedInOverworld |
P199495
|
FINISHED |
| Object | true |
—
|
LITERAL 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: true | Statement: [Eye of Ender, canBeUsedInOverworld, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeUsedInOverworld Context triple: [Eye of Ender, canBeUsedInOverworld, true]
-
A.
hasOverworld
Indicates that an entity possesses or is associated with a specific overworld environment or primary world context.
-
B.
canSpawnInDaylight
Indicates that the entity is able to spawn or appear during daylight conditions, rather than being restricted to darkness or nighttime.
-
C.
isNonOverworldBiome
Indicates that a biome exists outside the primary or standard overworld dimension of the game world.
-
D.
isLocatedInBiome
Indicates that one entity is situated within or belongs to the environmental region or biome represented by another entity.
-
E.
canGenerateInBiome
Indicates that an entity has the ability or is allowed to be generated or spawned within a specified biome.
- F. None of above. chosen
Provenance (4 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_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
| PDg | Predicate description generation | batch_69ff3e16527c81908c8d89da704ce012 |
completed | May 9, 2026, 2 p.m. |
Created at: May 3, 2026, 4:18 p.m.