Triple
T26126483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandra |
E659118
|
entity |
| Predicate | roleInAstrology |
P180924
|
FINISHED |
| Object | significator of mind |
—
|
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: significator of mind | Statement: [Chandra, roleInAstrology, significator of mind]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInAstrology Context triple: [Chandra, roleInAstrology, significator of mind]
-
A.
zodiacRole
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.
birthHouseSignificance
Indicates the importance or influence attributed to the house where a person was born within a given belief, cultural, or astrological system.
-
D.
positionInZodiac
Indicates the specific place or rank an entity occupies within the ordered sequence of zodiac signs.
-
E.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
- 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_69ee5bc2b2948190b458ad3f580af779 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 26, 2026, 8:12 p.m.