Triple
T37462023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C’Thun Warrior |
E930940
|
entity |
| Predicate | gamePlanEarly |
P44446
|
FINISHED |
| Object | play C’Thun buff minions |
—
|
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 C’Thun buff minions | Statement: [C’Thun Warrior, gamePlanEarly, play C’Thun buff minions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gamePlanEarly Context triple: [C’Thun Warrior, gamePlanEarly, play C’Thun buff minions]
-
A.
postGamesPlan
Indicates that an entity publishes or shares a plan or strategy related to games after they have concluded.
-
B.
partOfPlan
Indicates that one entity is included as a component or step within a broader plan or strategy.
-
C.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
D.
earlyStrategy
chosen
Indicates that an entity adopts or implements a strategy at an early stage or time relative to a process, event, or development.
-
E.
planningProcess
Indicates a relationship where an entity is engaged in or associated with the structured activity of defining goals, strategies, and steps to achieve a desired outcome.
- 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_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.