Triple
T37461531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C’Thun’s Chosen |
E930928
|
entity |
| Predicate | boostsLocation |
P67079
|
FINISHED |
| Object | wherever C’Thun is |
—
|
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: wherever C’Thun is | Statement: [C’Thun’s Chosen, boostsLocation, wherever C’Thun is]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boostsLocation Context triple: [C’Thun’s Chosen, boostsLocation, wherever C’Thun is]
-
A.
agingLocation
Indicates the place where an entity undergoes an aging process or is stored to age over time.
-
B.
featuresLocation
Indicates that something is characterized by or includes a specific location as one of its notable attributes.
-
C.
benefitOfLocation
chosen
Indicates that a particular location provides an advantage, positive effect, or beneficial quality to an entity or activity.
-
D.
possibleLocation
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
E.
loreLocation
Indicates that something is the place or setting where related background story, history, or world-building information is situated or associated.
- 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_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.