Triple
T37662156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicken Jockey |
E937739
|
entity |
| Predicate | immuneToFallDamage |
P100262
|
FINISHED |
| Object | baby zombie is protected from fall damage by 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: baby zombie is protected from fall damage by chicken | Statement: [Chicken Jockey, immuneToFallDamage, baby zombie is protected from fall damage by chicken]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: immuneToFallDamage Context triple: [Chicken Jockey, immuneToFallDamage, baby zombie is protected from fall damage by chicken]
-
A.
teleportTriggersFallDamage
Indicates that using teleportation causes the affected entity to incur fall damage.
-
B.
cannotBeDamagedBy
chosen
Indicates that one entity is immune to harm, injury, or degradation caused by another specified entity or factor.
-
C.
hasRoleInImmunity
Indicates that an entity functions in or contributes to an immune-related process or mechanism.
-
D.
takesDamageFrom
Indicates that one entity receives or suffers damage as a result of an action, effect, or interaction caused by another entity.
-
E.
damageTakenPerJump
Indicates the amount of damage an entity receives each time it performs a jump.
- 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_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.