Triple
T38592190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarab Lord |
E932478
|
entity |
| Predicate | associatedWithBoss |
P196728
|
FINISHED |
| Object | C'Thun |
E2281536
|
NE 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 | Statement: [Scarab Lord, associatedWithBoss, C'Thun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithBoss Context triple: [Scarab Lord, associatedWithBoss, C'Thun]
-
A.
hasBoss
Indicates that one entity serves as the direct superior or manager of another entity in a hierarchical relationship.
-
B.
hasBossMember
Indicates that one entity serves as the boss or superior of another entity within an organizational or hierarchical structure.
-
C.
associatedWithManager
Indicates that an entity has a managerial connection or relationship with a specific manager.
-
D.
associatedWithInWork
Indicates that two entities are connected or related to each other within the context of a particular work or project.
-
E.
hasBossForm
chosen
Indicates that an entity has a special, typically more powerful "boss" version or transformation form.
- F. None of above.
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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a423f71f740819082c9c08a9693a4aa |
completed | June 29, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.