Triple
T37664618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skeleton (Java Edition, certain conditions) |
E937792
|
entity |
| Predicate | canSpawnOnBlock |
P192021
|
FINISHED |
| Object | solid block |
—
|
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: solid block | Statement: [Skeleton (Java Edition, certain conditions), canSpawnOnBlock, solid block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSpawnOnBlock Context triple: [Skeleton (Java Edition, certain conditions), canSpawnOnBlock, solid block]
-
A.
cannotSpawnOn
Indicates that an entity is not allowed or able to be generated, created, or appear on a specified surface or location.
-
B.
canSpawnFromSpawner
Indicates that an entity is able to be generated or created by a specified spawner mechanism.
-
C.
canGenerateInBiome
Indicates that an entity has the ability or is allowed to be generated or spawned within a specified biome.
-
D.
canSpawnInStructure
Indicates that an entity or object is able to appear or be generated within a specified structure or building type.
-
E.
canSpawnWith
Indicates that one entity is able to appear, be created, or originate in conjunction with another entity under the same conditions or context.
- 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_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
| PDg | Predicate description generation | batch_69fcf1b241888190a243f07051c71383 |
completed | May 7, 2026, 8:10 p.m. |
Created at: May 3, 2026, 4:18 p.m.