Triple
T37461526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C’Thun’s Chosen |
E930928
|
entity |
| Predicate | hasSetKeyword |
P202469
|
FINISHED |
| Object | Old Gods synergy |
—
|
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: Old Gods synergy | Statement: [C’Thun’s Chosen, hasSetKeyword, Old Gods synergy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSetKeyword Context triple: [C’Thun’s Chosen, hasSetKeyword, Old Gods synergy]
-
A.
hasKeyWork
Indicates that an entity possesses or is associated with a primary or central work (such as a main publication, artwork, or project) that is especially representative or important.
-
B.
hasExampleKeyword
Indicates that something is associated with or contains a specific example keyword.
-
C.
hasBCPKeyword
Indicates that an entity is associated with, labeled by, or contains a specific BCP (Business Continuity Plan) keyword.
-
D.
hasExpansionKeyword
Indicates that an entity is associated with a keyword used to expand or broaden search, query, or matching criteria.
-
E.
hasKeyAct
Indicates that one entity possesses or is associated with a primary or central action related to another entity.
- 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_6a0082989e6c819099fea0e706332e37 |
completed | May 10, 2026, 1:05 p.m. |
| PD | Predicate disambiguation | batch_6a0081ed6a1481908baf472876e28db9 |
completed | May 10, 2026, 1:02 p.m. |
| PDg | Predicate description generation | batch_6a008297ad4c81909ee2e713d2c754d1 |
completed | May 10, 2026, 1:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.