Triple
T26126482
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandra |
E659118
|
entity |
| Predicate | associatedWithAstrology |
P94582
|
FINISHED |
| Object | Vedic astrology |
—
|
NE NERFINISHED |
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: Vedic astrology | Statement: [Chandra, associatedWithAstrology, Vedic astrology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithAstrology Context triple: [Chandra, associatedWithAstrology, Vedic astrology]
-
A.
roleInAstrology
Indicates the specific function, influence, or significance that something holds within an astrological system or interpretation.
-
B.
birthHouseSignificance
Indicates the importance or influence attributed to the house where a person was born within a given belief, cultural, or astrological system.
-
C.
zodiacRelation
Indicates a relationship between entities based on their positions or compatibility within the zodiac or astrological system.
-
D.
isUsedInAstrology
chosen
Indicates that something is employed or applied within the practice, methods, or interpretations of astrology.
-
E.
zodiacModality
Indicates the astrological modality (cardinal, fixed, or mutable) associated with a given zodiac sign.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: April 26, 2026, 8:12 p.m.