Triple
T3743071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rabbi |
E79745
|
entity |
| Predicate | ordinationRequires |
P51209
|
FINISHED |
| Object | intensive study |
—
|
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: intensive study | Statement: [Rabbi, ordinationRequires, intensive study]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordinationRequires Context triple: [Rabbi, ordinationRequires, intensive study]
-
A.
ordination
Indicates the formal conferral of religious authority or office upon a person within a religious tradition.
-
B.
approvalRequirement
Indicates that one entity must grant permission or authorization before another entity’s action, decision, or state change can proceed.
-
C.
appointmentRequirement
Indicates that a particular action, service, or interaction can only occur if an appointment has been scheduled or a specified appointment condition is met.
-
D.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
E.
requiresDispositionOf
Indicates that one entity must be appropriately handled, removed, or otherwise disposed of as a condition related to another entity or situation.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb576b5881908515d64c71f11a16 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc198b95481908ca6e4e875aae446 |
completed | March 8, 2026, 6:36 p.m. |
Created at: March 8, 2026, 3:34 p.m.