Triple
T3835001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gersonides |
E91107
|
entity |
| Predicate | viewOnAstrology |
P13276
|
FINISHED |
| Object | accepted a qualified form of astrology |
—
|
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: accepted a qualified form of astrology | Statement: [Gersonides, viewOnAstrology, accepted a qualified form of astrology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: viewOnAstrology Context triple: [Gersonides, viewOnAstrology, accepted a qualified form of astrology]
-
A.
starSign
Indicates the astrological zodiac sign associated with a person or entity based on their birth date.
-
B.
positionInZodiac
Indicates the specific place or rank an entity occupies within the ordered sequence of zodiac signs.
-
C.
zodiacSystem
Indicates a relationship where an entity is associated with, defined by, or classified under a particular zodiac system or framework.
-
D.
viewOnFate
chosen
Indicates a relationship where one entity holds a particular belief, attitude, or perspective about fate or predestination.
-
E.
viewOnSun
Indicates a relationship where an entity has a particular perspective, opinion, or stance regarding the sun.
- 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_69aed960b538819096561c8ed448dec9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeb8a27688190866bc41441e2260c |
completed | March 9, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69aee74dcecc819098285483ec721b40 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.