Triple
T37661756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wither Skeleton Skull |
E937732
|
entity |
| Predicate | canBeObtainedIn |
P154561
|
FINISHED |
| Object | Survival mode |
—
|
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: Survival mode | Statement: [Wither Skeleton Skull, canBeObtainedIn, Survival mode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeObtainedIn Context triple: [Wither Skeleton Skull, canBeObtainedIn, Survival mode]
-
A.
canBeObtainedFrom
Indicates that one entity is derivable, producible, or acquirable from another entity as a source or origin.
-
B.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
-
C.
mayBeAvailableIn
chosen
Indicates that an entity has the potential to be obtainable, accessible, or present within a specified context, location, or medium.
-
D.
canBePurchased
Indicates that one entity is available to be bought or acquired in exchange for payment by another entity.
-
E.
canBeEarnedBy
Indicates that something (such as a reward, status, or resource) is obtainable through the actions, efforts, or qualifications of a particular entity.
- 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_69ff45793d5c81909dc503ad1f714ee2 |
completed | May 9, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69ff41cb0e088190a6e9b03cb20e5fad |
completed | May 9, 2026, 2:16 p.m. |
Created at: May 3, 2026, 4:18 p.m.