Triple
T37661758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wither Skeleton Skull |
E937732
|
entity |
| Predicate | usedInAdvancement |
P199385
|
FINISHED |
| Object | Spooky Scary Skeletons |
—
|
NE NERFINISHED |
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: Spooky Scary Skeletons | Statement: [Wither Skeleton Skull, usedInAdvancement, Spooky Scary Skeletons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInAdvancement Context triple: [Wither Skeleton Skull, usedInAdvancement, Spooky Scary Skeletons]
-
A.
areUsedIn
Indicates that certain entities serve as components, tools, or resources within a particular process, context, or application.
-
B.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
C.
usedInDescriptionOf
Indicates that one entity is employed as part of the descriptive content or explanation of another entity.
-
D.
usedInStructure
Indicates that something (such as a material, component, or element) is employed as part of the composition or construction of a larger structure.
-
E.
usedInStage
Indicates that something is utilized or applied during a particular stage or phase of a process or workflow.
- 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_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
| PDg | Predicate description generation | batch_69ff32b6dd448190a7a6ebb76b99d4cc |
completed | May 9, 2026, 1:12 p.m. |
Created at: May 3, 2026, 4:18 p.m.