Triple
T37661751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wither Skeleton Skull |
E937732
|
entity |
| Predicate | lootTableSource |
P100838
|
FINISHED |
| Object | Wither Skeleton entity loot table |
—
|
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: Wither Skeleton entity loot table | Statement: [Wither Skeleton Skull, lootTableSource, Wither Skeleton entity loot table]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lootTableSource Context triple: [Wither Skeleton Skull, lootTableSource, Wither Skeleton entity loot table]
-
A.
lootSourceFor
Indicates that one entity takes or extracts loot, valuables, or resources from another entity as the source.
-
B.
lootTableIncludes
chosen
Indicates that a particular loot table contains or can yield a specified item or reward.
-
C.
lootContext
Indicates the situational circumstances or environment in which the looting action occurs or is relevant.
-
D.
LootType
Indicates the type or category of loot associated with an entity or event.
-
E.
loreSourceType
Indicates the type or category of source from which a piece of lore or background information is derived.
- 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_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.