Triple
T37769186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piglin Brute |
E941493
|
entity |
| Predicate | doesNotFlee |
P4300
|
FINISHED |
| Object | zombified piglin |
—
|
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: zombified piglin | Statement: [Piglin Brute, doesNotFlee, zombified piglin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: doesNotFlee Context triple: [Piglin Brute, doesNotFlee, zombified piglin]
-
A.
fleesWith
Indicates that one entity escapes or runs away together with another entity, sharing the act of fleeing as companions or partners.
-
B.
fleesTo
Indicates that an entity escapes or runs away from a place, situation, or threat and goes to a specific destination.
-
C.
cannotDieInHumanSense
Indicates that the entity is not subject to death or mortality in the way humans experience or understand it.
-
D.
doesNot
chosen
Indicates that a specified entity lacks, refrains from, or fails to perform a particular action or exhibit a particular property in relation to another entity or context.
-
E.
doesNotTry
Indicates that an entity makes no attempt to perform a particular action or engage in a specified activity.
- 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_69f76ee3251881909bb4451aad50752b |
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:19 p.m.