Triple
T16417736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaia Data Release 2 |
E398732
|
entity |
| Predicate | astrometricReferenceEpoch |
P21934
|
FINISHED |
| Object | J2015.5 |
—
|
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: J2015.5 | Statement: [Gaia Data Release 2, astrometricReferenceEpoch, J2015.5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: astrometricReferenceEpoch Context triple: [Gaia Data Release 2, astrometricReferenceEpoch, J2015.5]
-
A.
equatorialCoordinateEpoch
Indicates the specific reference date or epoch at which an object's equatorial coordinates (right ascension and declination) are defined or valid.
-
B.
epochReference
chosen
Indicates a temporal relationship where one time expression is interpreted relative to a specified reference epoch or baseline time.
-
C.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
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.
perihelionYear
Indicates the specific calendar year in which an object's orbit brings it to perihelion, its closest point to the Sun.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e328798a488190a5fad01c3c95584c |
completed | April 18, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:09 a.m.