Triple
T19850499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kohen |
E476978
|
entity |
| Predicate | honorInSynagogue |
P137569
|
FINISHED |
| Object | called first to the Torah |
—
|
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: called first to the Torah | Statement: [Kohen, honorInSynagogue, called first to the Torah]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honorInSynagogue Context triple: [Kohen, honorInSynagogue, called first to the Torah]
-
A.
mainSynagogue
Indicates that one entity serves as the primary or principal synagogue associated with another entity (such as a place, community, or organization).
-
B.
hasSynagogueType
Indicates the specific classification or type of synagogue associated with an entity.
-
C.
synagogueDate
Indicates the date associated with a synagogue, such as its construction, dedication, or another significant event in its history.
-
D.
hasSynagogueUnion
Indicates that there exists an organizational or formal union connecting one synagogue with another synagogue or group of synagogues.
-
E.
eraWithinJudaism
Indicates that a time period or era occurs within, or is defined as part of, the broader historical or religious framework of Judaism.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65867b5408190bbd12ca567c4705f |
completed | April 20, 2026, 4:46 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:51 p.m.