Triple
T5581526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgo |
E146650
|
entity |
| Predicate | zodiacSpan |
P64567
|
FINISHED |
| Object | 150° to 180° of the ecliptic |
—
|
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: 150° to 180° of the ecliptic | Statement: [Virgo, zodiacSpan, 150° to 180° of the ecliptic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zodiacSpan Context triple: [Virgo, zodiacSpan, 150° to 180° of the ecliptic]
-
A.
zodiacSystem
Indicates a relationship where an entity is associated with, defined by, or classified under a particular zodiac system or framework.
-
B.
positionInZodiac
Indicates the specific place or rank an entity occupies within the ordered sequence of zodiac signs.
-
C.
zodiacRelation
Indicates a relationship between entities based on their positions or compatibility within the zodiac or astrological system.
-
D.
zodiacStatus
Indicates the astrological state or classification of an entity within the zodiac system (e.g., sign, phase, or related status).
-
E.
isZodiacConstellation
Indicates that one entity is a constellation that belongs to the set of zodiac constellations through which the Sun appears to move over the course of a year.
- 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_69c0090287a08190b4098411effe970c |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0208147a48190b2cdb42b9c9814a3 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:37 p.m.