Triple
T12104165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Κάνωπος |
E288260
|
entity |
| Predicate | equatorialCoordinatesEpoch |
P66369
|
FINISHED |
| Object | J2000 |
—
|
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: J2000 | Statement: [Κάνωπος, equatorialCoordinatesEpoch, J2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: equatorialCoordinatesEpoch Context triple: [Κάνωπος, equatorialCoordinatesEpoch, J2000]
-
A.
equatorialCoordinateEpoch
chosen
Indicates the specific reference date or epoch at which an object's equatorial coordinates (right ascension and declination) are defined or valid.
-
B.
equatorialCoordinateSystem
Indicates a relationship where an object's position is specified using the equatorial coordinate system, typically defined by right ascension and declination relative to the celestial equator.
-
C.
endDateSidereal
Indicates the date and time, measured in sidereal rather than solar terms, at which a specified event, state, or interval comes to an end.
-
D.
calendarEpoch
Indicates the reference starting point in time from which a particular calendar system counts its dates.
-
E.
startDateSidereal
Indicates the sidereal (star-based) date on which an event, period, or state begins.
- 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_69d6ab4a5c448190a110d1273314b21a |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9164ada5081908676bd9e5947268a |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150497408190921334d21503375a |
completed | April 10, 2026, 3:19 p.m. |
Created at: April 8, 2026, 9:48 p.m.