Triple
T26126573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budha |
E659120
|
entity |
| Predicate | astrologicalRole |
P57115
|
FINISHED |
| Object | karaka (significator) for business |
—
|
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: karaka (significator) for business | Statement: [Budha, astrologicalRole, karaka (significator) for business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: astrologicalRole Context triple: [Budha, astrologicalRole, karaka (significator) for business]
-
A.
zodiacRole
chosen
Indicates the specific role, function, or symbolic position an entity holds within a zodiac system or zodiac sign context.
-
B.
roleInConstellation
Indicates the specific function or position an entity holds within a particular constellation.
-
C.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
D.
roleInTheProphecy
Indicates that an entity holds a specific function, status, or significance within the context of a particular prophecy.
-
E.
birthHouseSignificance
Indicates the importance or influence attributed to the house where a person was born within a given belief, cultural, or astrological system.
- 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_69f60b8eeeb48190a192fa8ba8cc20bf |
completed | May 2, 2026, 2:34 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 8:12 p.m.