Triple
T2209730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Spatial Reference System |
E50885
|
entity |
| Predicate | referenceEpoch |
P21934
|
FINISHED |
| Object | time-dependent coordinates |
—
|
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: time-dependent coordinates | Statement: [National Spatial Reference System, referenceEpoch, time-dependent coordinates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: referenceEpoch Context triple: [National Spatial Reference System, referenceEpoch, time-dependent coordinates]
-
A.
epochReference
chosen
Indicates a temporal relationship where one time expression is interpreted relative to a specified reference epoch or baseline time.
-
B.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
C.
referenceMeridian
Indicates that one location, measurement, or coordinate system is defined or interpreted relative to a specified meridian used as its longitudinal reference.
-
D.
isEpochBoundaryFor
Indicates that something marks or defines the transition point between two distinct epochs for another entity.
-
E.
timeOffsetReference
Indicates that a temporal value is specified relative to a particular reference time or event, defining the offset between them.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc1baa0948190b07ffc347a4f714e |
completed | March 7, 2026, 6:12 a.m. |
| PD | Predicate disambiguation | batch_69abbda8a6dc8190aa855ce2d17194b1 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.