Triple
T37514936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marauder (Path of Exile) |
E932610
|
entity |
| Predicate | startingAttribute |
P20799
|
FINISHED |
| Object | high Strength |
—
|
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: high Strength | Statement: [Marauder (Path of Exile), startingAttribute, high Strength]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startingAttribute Context triple: [Marauder (Path of Exile), startingAttribute, high Strength]
-
A.
startsAs
Indicates that an entity initially exists or appears in a particular form, state, or role before potentially changing to another.
-
B.
initialTrait
chosen
Indicates that a particular trait or characteristic is present in an entity at the beginning of a process, state, or time period.
-
C.
coreAttribute
Indicates that one attribute is a fundamental, defining, or essential property of another entity.
-
D.
initialAttitude
Indicates the starting stance, feeling, or disposition one entity holds toward another or toward a situation before any interaction or change occurs.
-
E.
startingGuard
Indicates that an entity serves as the primary or first-choice guard in a lineup, formation, or configuration.
- 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_6a00d76d0e0881908d83a8dcce511167 |
completed | May 10, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_6a00d711805881909a94cfd1f25fb331 |
completed | May 10, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.