Triple
T37472459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanguine Depths |
E931186
|
entity |
| Predicate | bossRole |
P98692
|
FINISHED |
| Object | General Kaal is a Stone Legion general |
—
|
NE NERFINISHED |
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: General Kaal is a Stone Legion general | Statement: [Sanguine Depths, bossRole, General Kaal is a Stone Legion general]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bossRole Context triple: [Sanguine Depths, bossRole, General Kaal is a Stone Legion general]
-
A.
basisRole
Indicates that one role serves as the foundational or underlying role upon which another role or function is defined or derived.
-
B.
bossCharacter
chosen
Indicates that one character serves as the primary, often more powerful, opponent or leader that others must confront or overcome.
-
C.
ownerRole
Indicates the role or capacity in which an entity serves as the owner of another entity.
-
D.
agencyRole
Indicates that one entity serves in a specific functional or organizational capacity on behalf of, or within, another entity (such as an agency, institution, or governing body).
-
E.
managementRole
Indicates that one entity holds a managerial or supervisory role with authority and responsibility over another entity.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8e62aa348190af235cc01ca98b02 |
completed | May 6, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0c53c08190b64291bac58cdb4c |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.