Triple
T19932126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ophiuchus |
E479079
|
entity |
| Predicate | zodiacSignStatus |
P59392
|
FINISHED |
| Object | not a traditional astrological sign |
—
|
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: not a traditional astrological sign | Statement: [Ophiuchus, zodiacSignStatus, not a traditional astrological sign]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zodiacSignStatus Context triple: [Ophiuchus, zodiacSignStatus, not a traditional astrological sign]
-
A.
zodiacStatus
chosen
Indicates the astrological state or classification of an entity within the zodiac system (e.g., sign, phase, or related status).
-
B.
positionInZodiac
Indicates the specific place or rank an entity occupies within the ordered sequence of zodiac signs.
-
C.
zodiacSpan
Indicates the range or period of dates during which a particular zodiac sign is considered to apply.
-
D.
zodiacRelation
Indicates a relationship between entities based on their positions or compatibility within the zodiac or astrological system.
-
E.
hasZodiacSignPart
Indicates that one entity is a component, segment, or subdivision of a zodiac sign represented by the other entity.
- 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_69d8e521855c8190b41871700afc8d6a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a14a2348190b41f8e320fe661d6 |
completed | April 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69e537f070b481908958e0e5911dcdc1 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.