Triple
T37462026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C’Thun Warrior |
E930940
|
entity |
| Predicate | gamePlanLate |
P190109
|
FINISHED |
| Object | play a heavily buffed C’Thun for lethal 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: play a heavily buffed C’Thun for lethal damage | Statement: [C’Thun Warrior, gamePlanLate, play a heavily buffed C’Thun for lethal damage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gamePlanLate Context triple: [C’Thun Warrior, gamePlanLate, play a heavily buffed C’Thun for lethal damage]
-
A.
laterGoal
Indicates that one goal occurs or is intended to be achieved after another goal in time.
-
B.
laterIn
Indicates that one event, state, or time point occurs after another in temporal order.
-
C.
postGamesPlan
Indicates that an entity publishes or shares a plan or strategy related to games after they have concluded.
-
D.
delayedBy
Indicates that one event, process, or action occurs later than expected or planned due to the influence or interference of another factor or entity.
-
E.
lastPlan
Indicates that one plan is the final or most recent plan in a sequence of plans associated with an entity or process.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69fcab6d41a88190a3576b4b088dcabd |
completed | May 7, 2026, 3:10 p.m. |
Created at: May 3, 2026, 4:17 p.m.