Triple
T982979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Atomic Time |
E21211
|
entity |
| Predicate | scaleUnit |
P18870
|
FINISHED |
| Object | second |
—
|
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: second | Statement: [International Atomic Time, scaleUnit, second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scaleUnit Context triple: [International Atomic Time, scaleUnit, second]
-
A.
nativeUnit
Indicates that one unit is the original, inherent, or default measurement unit associated with a given quantity or entity.
-
B.
standardUnitRelation
Indicates a relationship where one unit is defined, measured, or interpreted in terms of a recognized standard unit.
-
C.
timeScaleUnit
chosen
Indicates the unit of temporal measurement (such as seconds, minutes, or hours) used to express a given time scale.
-
D.
typeOfUnit
Indicates that one entity specifies the kind or category of measurement unit that the other entity belongs to.
-
E.
magnitudeScale
Indicates the scale or measurement system used to quantify the magnitude or intensity of something.
- 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_69a493c383dc8190a03257f22d4b4183 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b49284ac8190b1d7c828d728893c |
completed | March 1, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69a4b2aa219081908a6b0ef786b4aa52 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.