Triple
T37457025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elementals (Hearthstone) |
E930824
|
entity |
| Predicate | hasSubtypeExamples |
P1259
|
FINISHED |
| Object | Fire Elemental |
—
|
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: Fire Elemental | Statement: [Elementals (Hearthstone), hasSubtypeExamples, Fire Elemental]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubtypeExamples Context triple: [Elementals (Hearthstone), hasSubtypeExamples, Fire Elemental]
-
A.
hasExampleType
Indicates that something is associated with a specific type or category of example that characterizes or illustrates it.
-
B.
hasSubdivisionExample
Indicates that one entity is an example or instance of a subdivision or component part of another entity.
-
C.
hasMultipleSubclasses
Indicates that a class or category is related to more than one distinct subclass within a hierarchy.
-
D.
hasExample
chosen
Indicates that one entity serves as an instance, illustration, or concrete example of another entity.
-
E.
hasStructuralSubtype
Indicates that one structure is a more specific, subordinate form or subtype of another structure within a structural hierarchy.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a004d0b46148190bcec4ea67acfe170 |
completed | May 10, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_6a004c92283081909f229c1720af155a |
completed | May 10, 2026, 9:14 a.m. |
Created at: May 3, 2026, 4:17 p.m.