Triple

T33566782
Position Surface form Disambiguated ID Type / Status
Subject NATRF2022 E859780 entity
Predicate referenceEpochDefinition P21934 FINISHED
Object coordinates specified at reference epoch 2020.00 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: coordinates specified at reference epoch 2020.00 | Statement: [NATRF2022, referenceEpochDefinition, coordinates specified at reference epoch 2020.00]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: referenceEpochDefinition
Context triple: [NATRF2022, referenceEpochDefinition, coordinates specified at reference epoch 2020.00]
  • A. epochReference chosen
    Indicates a temporal relationship where one time expression is interpreted relative to a specified reference epoch or baseline time.
  • B. mappingEpoch
    Indicates the specific time period or version during which a particular mapping or correspondence between entities is defined or valid.
  • C. calendarEpoch
    Indicates the reference starting point in time from which a particular calendar system counts its dates.
  • D. DecEpoch
    Indicates the specific point in time (epoch) at which a declination (Dec) measurement or coordinate value is defined or referenced.
  • E. epochOfData
    Indicates the specific time period or epoch during which the referenced data was collected, generated, or considered valid.
  • 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_69f3497c1d288190a844ea699914e038 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69fddf721c1481909301a0f379368f10 completed May 8, 2026, 1:04 p.m.
PD Predicate disambiguation batch_69fddda1ae7c8190b5848ff9a9e39826 completed May 8, 2026, 12:57 p.m.
Created at: May 1, 2026, 1:40 a.m.