Triple
T23244503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 畢宿五 |
E581546
|
entity |
| Predicate | 赤道座標系 |
P24827
|
FINISHED |
| Object | J2000.0 |
—
|
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.0 | Statement: [畢宿五, 赤道座標系, J2000.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 赤道座標系 Context triple: [畢宿五, 赤道座標系, J2000.0]
-
A.
equatorialCoordinateSystem
chosen
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.
-
B.
equatorialCoordinateEpoch
Indicates the specific reference date or epoch at which an object's equatorial coordinates (right ascension and declination) are defined or valid.
-
C.
locatedNearCelestialEquator
Indicates that one celestial object or point lies close to the celestial equator in the sky.
-
D.
zodiacalAxis
Indicates a relationship where two zodiac signs or points lie directly opposite each other on the zodiac circle, forming a polar or complementary axis.
-
E.
celestialLongitude
Indicates the angular position of a celestial object along the ecliptic, measured eastward from a defined reference point such as the vernal equinox.
- 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_69e24606b17c81908aba1a4911c8a8ba |
completed | April 17, 2026, 2:39 p.m. |
| NER | Named-entity recognition | batch_69f193ee37c8819091f799506fa532da |
completed | April 29, 2026, 5:15 a.m. |
| PD | Predicate disambiguation | batch_69effcdadec0819092ec1749ee453b4e |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:10 p.m.