Triple
T37662161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicken Jockey |
E937739
|
entity |
| Predicate | canSpawnFromEgg |
P100798
|
FINISHED |
| Object | possible when a baby zombie mounts a newly spawned chicken |
—
|
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: possible when a baby zombie mounts a newly spawned chicken | Statement: [Chicken Jockey, canSpawnFromEgg, possible when a baby zombie mounts a newly spawned chicken]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSpawnFromEgg Context triple: [Chicken Jockey, canSpawnFromEgg, possible when a baby zombie mounts a newly spawned chicken]
-
A.
hasSpawnEgg
chosen
Indicates that an entity is associated with or can be generated by a specific spawn egg item.
-
B.
hasHatch
Indicates that one entity possesses or is equipped with a hatch, such as an opening or access panel.
-
C.
eggHatchedBy
Indicates that an egg is brought to hatching by a specific agent or entity.
-
D.
canSpawnWith
Indicates that one entity is able to appear, be created, or originate in conjunction with another entity under the same conditions or context.
-
E.
hasHatches
Indicates that one entity possesses or is equipped with hatches (openable panels or doors).
- 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_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:18 p.m.