Triple
T37662100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zombie Villager (Minecraft) |
E937738
|
entity |
| Predicate | canBeCured |
P199737
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zombie Villager (Minecraft), canBeCured, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeCured Context triple: [Zombie Villager (Minecraft), canBeCured, true]
-
A.
hasCure
Indicates that one entity serves as a remedy or treatment that can eliminate or effectively counteract a disease, condition, or problem affecting another entity.
-
B.
curedWith
Indicates that one entity is treated or healed by using another entity as the remedy or therapeutic method.
-
C.
hasRemedy
Indicates that one entity serves as a remedy, treatment, or corrective measure for a problem, condition, or undesirable state associated with another entity.
-
D.
doesNotCure
Indicates that an action, treatment, or intervention fails to eliminate or resolve a condition, problem, or disease in the affected entity.
-
E.
toBeHealedIn
Indicates that an entity undergoes or receives healing within a specified context, place, or medium.
- 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_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
| PDg | Predicate description generation | batch_69ff528536d481909caefe52fcd8aaa7 |
completed | May 9, 2026, 3:28 p.m. |
Created at: May 3, 2026, 4:18 p.m.