Triple
T15847048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabbenu Tam |
E384239
|
entity |
| Predicate | relationshipToRashi |
P120105
|
FINISHED |
| Object | grandson |
—
|
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: grandson | Statement: [Rabbenu Tam, relationshipToRashi, grandson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipToRashi Context triple: [Rabbenu Tam, relationshipToRashi, grandson]
-
A.
zodiacRelation
Indicates a relationship between entities based on their positions or compatibility within the zodiac or astrological system.
-
B.
positionInZodiac
Indicates the specific place or rank an entity occupies within the ordered sequence of zodiac signs.
-
C.
isZodiacConstellationMember
Indicates that an entity belongs to the set of constellations that make up the traditional zodiac.
-
D.
zodiacPolarity
Indicates the complementary energetic relationship (positive/negative or active/receptive) associated with a zodiac sign within an astrological system.
-
E.
zodiacModality
Indicates the astrological modality (cardinal, fixed, or mutable) associated with a given zodiac sign.
- 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e14ca7c8f08190abe21cbb0c390f95 |
completed | April 16, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69e005434ed88190baf11c169da3cf29 |
completed | April 15, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69e007869ae481909473ee220a7ccdb5 |
completed | April 15, 2026, 9:47 p.m. |
Created at: April 10, 2026, 4:50 a.m.