Triple
T37554380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Judgement Legplates |
E933659
|
entity |
| Predicate | setBonusAssociation |
P5268
|
FINISHED |
| Object | Judgement Armor set bonuses |
—
|
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: Judgement Armor set bonuses | Statement: [Judgement Legplates, setBonusAssociation, Judgement Armor set bonuses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setBonusAssociation Context triple: [Judgement Legplates, setBonusAssociation, Judgement Armor set bonuses]
-
A.
supportsBonus
chosen
Indicates that one entity provides or enables an additional benefit, reward, or bonus for another entity.
-
B.
tierSetAssociation
Indicates an association that links an entity to a specific tier or tier set within a tiered structure or classification.
-
C.
functionAssociation
Indicates that one entity is associated with, implements, or is linked to a particular function or functional role of another entity.
-
D.
associatedWithAssociation
Indicates a relationship where an entity is linked or connected to a particular association or organization.
-
E.
awardAssociation
Indicates a relationship where an entity is connected to, or recognized by, a specific award or awarding body.
- 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_69f76eca55bc8190acf25741793d5dac |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.