Triple
T2683536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 26th General Conference on Weights and Measures |
E57428
|
entity |
| Predicate | redefinedUnit |
P9775
|
FINISHED |
| Object | kilogram |
—
|
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: kilogram | Statement: [26th General Conference on Weights and Measures, redefinedUnit, kilogram]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redefinedUnit Context triple: [26th General Conference on Weights and Measures, redefinedUnit, kilogram]
-
A.
definesUnit
Indicates that one entity specifies the measurement unit or standard by which the value or quantity of another entity is expressed.
-
B.
wasRedefinedIn
chosen
Indicates that an existing entity or concept was modified, updated, or given a new definition at a particular time or in a specific context.
-
C.
basedUnit
Indicates that one unit is defined in terms of, or derived from, another more fundamental unit.
-
D.
convertedUnit
Indicates that one unit is the result of converting a quantity expressed in another unit.
-
E.
redefinitionYear
Indicates the year in which something was redefined, such as when its definition, scope, or formal status was officially changed.
- 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_69ab4a5028388190a36f3baf1588309e |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd9d7692c81909d8fd9ce3817161b |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81c9b4c81908e5e0da6ac5f828b |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.