Triple
T22999750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BD+18 2019 |
E572602
|
entity |
| Predicate | hasEclipticLongitudeRole |
P20370
|
FINISHED |
| Object | nearEcliptic |
—
|
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: nearEcliptic | Statement: [BD+18 2019, hasEclipticLongitudeRole, nearEcliptic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEclipticLongitudeRole Context triple: [BD+18 2019, hasEclipticLongitudeRole, nearEcliptic]
-
A.
hasEclipticLatitude
Indicates that one celestial object or point has a specified angular distance north or south of the ecliptic plane.
-
B.
celestialLongitude
Indicates the angular position of a celestial object along the ecliptic, measured eastward from a defined reference point such as the vernal equinox.
-
C.
eclipticLongitudeRange
Indicates that an entity’s ecliptic longitude lies within a specified angular range along the ecliptic.
-
D.
liesOnEcliptic
chosen
Indicates that the referenced object’s position is located on or very close to the plane of the ecliptic.
-
E.
orbitalLongitude
Indicates the angular position of an orbiting body along its orbital path, measured as longitude from a defined reference direction or point.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182f6484c8190bfe3f7ea894c43d8 |
completed | April 29, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.