Triple
T37471020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soul Cinders |
E931151
|
entity |
| Predicate | progressionRole |
P188683
|
FINISHED |
| Object | late Shadowlands legendary progression |
—
|
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: late Shadowlands legendary progression | Statement: [Soul Cinders, progressionRole, late Shadowlands legendary progression]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: progressionRole Context triple: [Soul Cinders, progressionRole, late Shadowlands legendary progression]
-
A.
gradingRole
Indicates that an entity has the role or responsibility of evaluating, scoring, or grading another entity’s work, performance, or output.
-
B.
hasCareerProgressionTo
Indicates that one role, position, or career stage naturally advances or transitions into another within a professional or occupational path.
-
C.
profileRole
Indicates the specific role or function an entity holds within a given profile or contextual configuration.
-
D.
subsequentRole
Indicates that one role or position is held after, and in succession to, another role or position.
-
E.
providedRole
Indicates that one entity has assigned or supplied a specific role or function 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fbacaea12c8190a4c99e64335f0e7e |
completed | May 6, 2026, 9:03 p.m. |
Created at: May 3, 2026, 4:17 p.m.