Triple
T37461990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C’Thun Druid |
E930939
|
entity |
| Predicate | classHeroExamples |
P1259
|
FINISHED |
| Object | Malfurion Stormrage |
—
|
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: Malfurion Stormrage | Statement: [C’Thun Druid, classHeroExamples, Malfurion Stormrage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classHeroExamples Context triple: [C’Thun Druid, classHeroExamples, Malfurion Stormrage]
-
A.
baseExamples
Indicates that something serves as a fundamental or illustrative example for understanding or demonstrating another concept, item, or case.
-
B.
hasExample
chosen
Indicates that one entity serves as an instance, illustration, or concrete example of another entity.
-
C.
codeExample
Indicates that one entity provides a snippet or sample of source code that illustrates how to use, implement, or demonstrate another entity.
-
D.
exampleClass
Indicates that the subject belongs to, is categorized under, or serves as an instance of a particular class or type.
-
E.
exampleType
Indicates that one entity serves as a representative or illustrative instance of the type or category defined by another 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:17 p.m.