Triple
T37664372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guardian (Minecraft) |
E937787
|
entity |
| Predicate | despawns |
P188651
|
FINISHED |
| Object | when far from player |
—
|
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: when far from player | Statement: [Guardian (Minecraft), despawns, when far from player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: despawns Context triple: [Guardian (Minecraft), despawns, when far from player]
-
A.
despawnRules
Indicates the conditions or rules under which an entity is removed or disappears from the game or system.
-
B.
spawns
Indicates that one entity generates, creates, or gives rise to another entity, often as an origin or source.
-
C.
dropsOnDeath
Indicates that when an entity dies, it releases or leaves behind a specified item or set of items.
-
D.
diesAfterSpawning
Indicates that an entity dies shortly after producing offspring or completing its spawning process.
-
E.
canDespawnNaturally
chosen
Indicates that an entity is able to disappear or be removed from the world through normal, automatic game mechanics rather than by explicit player or script actions.
- 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.