Triple
T22430396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gamma Orionis |
E554482
|
entity |
| Predicate | hasEquatorialCoordinatesEpoch |
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: [Gamma Orionis, hasEquatorialCoordinatesEpoch, J2000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEquatorialCoordinatesEpoch Context triple: [Gamma Orionis, hasEquatorialCoordinatesEpoch, 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.
hasEquinox
Indicates that an astronomical object or system possesses one or more equinox points or events in its orbital or rotational cycle.
-
D.
hasEquatorialRadius
Indicates that an entity has a specified radius measured at its equator.
-
E.
hasEquatorCrossing
Indicates that the path or orbit of an entity crosses the equator of a reference body.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a311b148190bdb752f3f067bb3f |
completed | April 29, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.