Triple
T37515154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadow (Path of Exile) |
E932614
|
entity |
| Predicate | ascendancySaboteurFocus |
P189506
|
FINISHED |
| Object | traps |
—
|
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: traps | Statement: [Shadow (Path of Exile), ascendancySaboteurFocus, traps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ascendancySaboteurFocus Context triple: [Shadow (Path of Exile), ascendancySaboteurFocus, traps]
-
A.
ascentStageFate
Indicates the outcome or final status of an ascent stage after it has completed its primary mission or operation.
-
B.
ascendancyClass
Indicates a hierarchical or rank-based classification that specifies an entity’s superior or dominant status relative to others.
-
C.
ascendedTo
Indicates that one entity rose, climbed, or moved upward to reach the position, level, or location of another entity.
-
D.
ascendancyClassType
Indicates the specific subclass or specialization category to which an entity’s ascendancy belongs.
-
E.
factionFocus
Indicates that an entity is primarily oriented toward, aligned with, or concentrated on a particular faction as its main focus.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:17 p.m.