Triple
T1206459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cancer |
E25899
|
entity |
| Predicate | eclipticLongitudeRange |
P24636
|
FINISHED |
| Object | 90° to 120° |
—
|
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: 90° to 120° | Statement: [Cancer, eclipticLongitudeRange, 90° to 120°]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eclipticLongitudeRange Context triple: [Cancer, eclipticLongitudeRange, 90° to 120°]
-
A.
rightAscensionRange
Indicates that an entity’s right ascension lies within a specified angular interval on the celestial sphere.
-
B.
orbitInclinationRange
Indicates the range of possible orbital inclination angles within which an object’s orbit is oriented relative to a reference plane.
-
C.
liesOnEcliptic
Indicates that the referenced object’s position is located on or very close to the plane of the ecliptic.
-
D.
inclinationToEcliptic
Indicates the angle between an object's orbital plane and the plane of the ecliptic, describing how tilted its orbit is relative to Earth's orbital plane.
-
E.
longitudeOfAscendingNode
Indicates the angular position of an orbit’s ascending node measured from a reference direction in the reference plane.
- F. None of above. chosen
Provenance (4 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bdc314c88190b1b5953834bfce7b |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6078088190ba0221ae3368416c |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bbf83584819088c69366f58586cc |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:46 p.m.