Triple
T23000235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libra |
E572612
|
entity |
| Predicate | zodiacLongitudeRange |
P24636
|
FINISHED |
| Object | 180° to 210° ecliptic longitude (approximate) |
—
|
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: 180° to 210° ecliptic longitude (approximate) | Statement: [Libra, zodiacLongitudeRange, 180° to 210° ecliptic longitude (approximate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zodiacLongitudeRange Context triple: [Libra, zodiacLongitudeRange, 180° to 210° ecliptic longitude (approximate)]
-
A.
zodiacSignRange
Indicates the span of calendar dates during which a particular zodiac sign is considered to apply.
-
B.
eclipticLongitudeRange
chosen
Indicates that an entity’s ecliptic longitude lies within a specified angular range along the ecliptic.
-
C.
hasZodiacSignRange
Indicates that there is an association between an entity and a specific span of dates corresponding to a zodiac sign or set of zodiac signs.
-
D.
zodiacSpan
Indicates the range or period of dates during which a particular zodiac sign is considered to apply.
-
E.
tropicalZodiacDates
Indicates the calendar date range during which each tropical zodiac sign is in effect.
- 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_69f18352bcf48190bd474eff69b3465b |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:50 p.m.