Triple
T37661932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Villager (Minecraft) |
E937735
|
entity |
| Predicate | canBeInfectedBy |
P51727
|
FINISHED |
| Object | zombie |
—
|
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: zombie | Statement: [Villager (Minecraft), canBeInfectedBy, zombie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeInfectedBy Context triple: [Villager (Minecraft), canBeInfectedBy, zombie]
-
A.
isPathogenOf
chosen
Indicates that one entity is a disease-causing agent (pathogen) that infects or causes illness in another entity.
-
B.
isInfestedWith
Indicates that one entity is overrun, occupied, or contaminated by another, typically unwanted, organism or agent.
-
C.
transmissibleTo
Indicates that something (such as a disease, signal, or property) can be passed or transferred from one entity to another.
-
D.
isReservoirOf
Indicates that one entity serves as a storage source or container holding a particular substance, resource, or quantity for another entity or purpose.
-
E.
isCarrierOf
Indicates that one entity serves as the bearer, holder, or transmitter of another entity (such as an object, substance, trait, or information).
- 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_69ff49f888348190b9c55afa73b99e6a |
completed | May 9, 2026, 2:51 p.m. |
| PD | Predicate disambiguation | batch_69ff49614ef88190ac70b034c55ad738 |
completed | May 9, 2026, 2:49 p.m. |
Created at: May 3, 2026, 4:18 p.m.