Triple
T37515151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadow (Path of Exile) |
E932614
|
entity |
| Predicate | ascendancyAssassinFocus |
P188697
|
FINISHED |
| Object | critical strikes |
—
|
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: critical strikes | Statement: [Shadow (Path of Exile), ascendancyAssassinFocus, critical strikes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ascendancyAssassinFocus Context triple: [Shadow (Path of Exile), ascendancyAssassinFocus, critical strikes]
-
A.
ascendancyClass
Indicates a hierarchical or rank-based classification that specifies an entity’s superior or dominant status relative to others.
-
B.
featuresAssassins
Indicates that the subject includes, portrays, or prominently involves assassins as part of its content or composition.
-
C.
ascendancyClassType
chosen
Indicates the specific subclass or specialization category to which an entity’s ascendancy belongs.
-
D.
ascensionMethod
Indicates the means or process by which an entity rises, advances, or transitions to a higher state, level, or position.
-
E.
ascentStageFate
Indicates the outcome or final status of an ascent stage after it has completed its primary mission or operation.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.