Triple
T38585217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patch 2.1 – Black Temple |
E932330
|
entity |
| Predicate | introducedSystemChanges |
P123179
|
FINISHED |
| Object | Resilience rating adjustments |
—
|
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: Resilience rating adjustments | Statement: [Patch 2.1 – Black Temple, introducedSystemChanges, Resilience rating adjustments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedSystemChanges Context triple: [Patch 2.1 – Black Temple, introducedSystemChanges, Resilience rating adjustments]
-
A.
changedSystem
Indicates that an entity has altered, replaced, or reconfigured a system from its previous state.
-
B.
introducedVotingSystemChange
Indicates that an entity initiated or implemented a modification to an existing voting system.
-
C.
featureChange
chosen
Indicates a modification in the properties, characteristics, or attributes of an entity between two states or points in time.
-
D.
introducedInSystem
Indicates that an entity was first added, implemented, or made available within a particular system.
-
E.
notableChange
Indicates a significant alteration or shift in the state, condition, or characteristics of an entity or relationship.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: May 3, 2026, 4:32 p.m.