Triple
T37514939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marauder (Path of Exile) |
E932610
|
entity |
| Predicate | associatedDefensiveStat |
—
|
GENERATED |
| Object | Armour |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
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 (1 batch)
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. |
Created at: May 3, 2026, 4:17 p.m.