Triple
T37462001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C’Thun Warrior |
E930940
|
entity |
| Predicate | primaryWinCondition |
P20842
|
FINISHED |
| Object | C’Thun battlecry damage |
—
|
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: C’Thun battlecry damage | Statement: [C’Thun Warrior, primaryWinCondition, C’Thun battlecry damage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryWinCondition Context triple: [C’Thun Warrior, primaryWinCondition, C’Thun battlecry damage]
-
A.
conditionOfVictory
chosen
Indicates the specific circumstances or criteria under which a participant is considered to have won.
-
B.
classWins
Indicates that a particular class has achieved victory or success in a competitive context.
-
C.
winnerWins
Indicates that the entity identified as the winner achieves victory over another entity or in a specified competition or event.
-
D.
mainWinningAlliance
Indicates that the referenced alliance is the primary winner in a competitive event or contest.
-
E.
winsFor
Indicates that one entity achieves victory or success on behalf of, or in favor of, 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_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.