Triple
T6549432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AOW |
E151092
|
entity |
| Predicate | adjustedBy |
P1121
|
FINISHED |
| Object | periodic legislative reforms |
—
|
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: periodic legislative reforms | Statement: [AOW, adjustedBy, periodic legislative reforms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjustedBy Context triple: [AOW, adjustedBy, periodic legislative reforms]
-
A.
adjustmentType
Indicates the specific kind or category of modification applied to an existing value, state, or configuration within the relationship.
-
B.
amendedBy
chosen
Indicates that one entity has been modified, revised, or updated as a result of changes made by another entity.
-
C.
amendedFor
Indicates that one entity has been modified or revised specifically to address, correct, or accommodate another entity.
-
D.
notAdjustedFor
Indicates that a value, measure, or result has not been modified or corrected to account for certain factors, conditions, or variables.
-
E.
fixedBy
Indicates that one entity is repaired, corrected, or resolved through the action or intervention of another entity.
- 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_69c687f3fd60819083bfa583e5bcfa71 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce07332481909a5a7964282eb776 |
completed | March 27, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69c6acf3e3708190b052ec774e607cb7 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:51 p.m.