Triple
T37661854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Player (Minecraft) |
E937734
|
entity |
| Predicate | defaultSpawnStructure |
P18866
|
FINISHED |
| Object | world spawn point |
—
|
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: world spawn point | Statement: [Player (Minecraft), defaultSpawnStructure, world spawn point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defaultSpawnStructure Context triple: [Player (Minecraft), defaultSpawnStructure, world spawn point]
-
A.
spawnStructure
Indicates that an entity causes a new structure to be created or instantiated in the environment.
-
B.
spawningLocation
chosen
Indicates the place or environment where an entity originates, appears, or is generated.
-
C.
dimensionSpawn
Indicates a relationship where an entity causes or initiates the creation or appearance of something within a specific dimension or realm.
-
D.
spawns
Indicates that one entity generates, creates, or gives rise to another entity, often as an origin or source.
-
E.
builtStructureFor
Indicates that one entity constructed or assembled a structure specifically intended for the use, benefit, or purpose of 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.