Triple
T37514939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marauder (Path of Exile) |
E932610
|
entity |
| Predicate | associatedDefensiveStat |
P205945
|
FINISHED |
| Object | Armour |
—
|
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: Armour | Statement: [Marauder (Path of Exile), associatedDefensiveStat, Armour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedDefensiveStat Context triple: [Marauder (Path of Exile), associatedDefensiveStat, Armour]
-
A.
defensiveRecord
Indicates a relationship where one entity documents, tracks, or summarizes the defensive performance or actions of another entity (such as a player, team, or system).
-
B.
defensiveSuccess
Indicates that a defensive action successfully prevented or mitigated an opposing threat, attack, or adverse outcome.
-
C.
defensiveSide
Indicates which entity is acting in a defensive role or position relative to another entity or situation.
-
D.
defensiveSynergyWith
Indicates a mutually reinforcing defensive relationship in which the protective effectiveness of each entity is enhanced by the presence or actions of the other.
-
E.
usedDefensiveLine
Indicates that an entity employed or deployed a particular defensive line as part of its strategy or actions.
- 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_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.