Triple
T37662099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zombie Villager (Minecraft) |
E937738
|
entity |
| Predicate | conversionChanceOnEasy |
P190732
|
FINISHED |
| Object | 0% |
—
|
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: 0% | Statement: [Zombie Villager (Minecraft), conversionChanceOnEasy, 0%]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conversionChanceOnEasy Context triple: [Zombie Villager (Minecraft), conversionChanceOnEasy, 0%]
-
A.
conversionChanceOnHard
Indicates the probability that a conversion will occur when conditions are classified as "hard" or at a higher difficulty level.
-
B.
conversionChanceOnNormal
Indicates the probability that a conversion will occur under normal or standard conditions.
-
C.
isEasierThan
Indicates that one entity requires less effort, difficulty, or complexity to accomplish, understand, or deal with than another entity.
-
D.
difficulty
Indicates the level of challenge, complexity, or effort required to perform an action, solve a problem, or achieve a particular outcome.
-
E.
hardnessOfBeatingRandom
Indicates how difficult it is to defeat or outperform something when its behavior or outcome is determined randomly.
- 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_69fcce2cf9188190b3f65b362203a6a3 |
completed | May 7, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
| PDg | Predicate description generation | batch_69fccdd2d84481909a7ce22407def9c7 |
completed | May 7, 2026, 5:37 p.m. |
Created at: May 3, 2026, 4:18 p.m.