Triple
T982978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Atomic Time |
E21211
|
entity |
| Predicate | epochReference |
P21934
|
FINISHED |
| Object | geocenter |
—
|
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: geocenter | Statement: [International Atomic Time, epochReference, geocenter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: epochReference Context triple: [International Atomic Time, epochReference, geocenter]
-
A.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
B.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
C.
timeOffsetReference
Indicates that a temporal value is specified relative to a particular reference time or event, defining the offset between them.
-
D.
referenceMeridian
Indicates that one location, measurement, or coordinate system is defined or interpreted relative to a specified meridian used as its longitudinal reference.
-
E.
chronologicalPosition
Indicates the relative ordering of one event or entity in time with respect to another.
- 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_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. |
| PDg | Predicate description generation | batch_69a4b345f890819092b51bf8128da461 |
completed | March 1, 2026, 9:44 p.m. |
Created at: March 1, 2026, 7:41 p.m.