Triple
T37662151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicken Jockey |
E937739
|
entity |
| Predicate | despawnRules |
P188622
|
FINISHED |
| Object | follows hostile mob despawn rules |
—
|
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: follows hostile mob despawn rules | Statement: [Chicken Jockey, despawnRules, follows hostile mob despawn rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: despawnRules Context triple: [Chicken Jockey, despawnRules, follows hostile mob despawn rules]
-
A.
deathGameRule
Indicates a rule or condition within a deadly or lethal game that governs how participants must act or what consequences they face.
-
B.
destroyedAfter
Indicates that one entity is destroyed at a point in time that occurs after the destruction of another entity.
-
C.
diesAfterSpawning
Indicates that an entity dies shortly after producing offspring or completing its spawning process.
-
D.
destroyedRegion
Indicates that an entity has caused the destruction or severe damage of a specified region.
-
E.
destroyedFor
Indicates that one entity was ruined, eliminated, or rendered unusable specifically for the benefit, purpose, or objective of another entity.
- 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_69fbaa19e4a88190b04f26c0d4e708fd |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbaa108ee48190b84d13df3ef3e365 |
completed | May 6, 2026, 8:52 p.m. |
Created at: May 3, 2026, 4:18 p.m.