Triple
T1463532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International System of Units |
E31565
|
entity |
| Predicate | redefinitionYear |
P28840
|
FINISHED |
| Object | 2019 |
—
|
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: 2019 | Statement: [International System of Units, redefinitionYear, 2019]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redefinitionYear Context triple: [International System of Units, redefinitionYear, 2019]
-
A.
renamedYear
Indicates the year in which an entity underwent a renaming or change of name.
-
B.
reclassificationYear
Indicates the year in which something was reassigned to a different category, status, or classification.
-
C.
reversionYear
Indicates the year in which something returns to a previous state, condition, or ownership.
-
D.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
E.
secondRedenominationYear
Indicates the year in which a second redenomination event (such as a currency or unit value reset) takes place.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c5b89708819084fb9ba4ff293b8b |
completed | March 1, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69a4c48121e48190946c23c583e5fb64 |
completed | March 1, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69a4c55508948190922aee3230a4323e |
completed | March 1, 2026, 11:01 p.m. |
Created at: March 1, 2026, 8 p.m.