Triple
T15886800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | dayan |
E385210
|
entity |
| Predicate | trainingOftenIncludes |
P10219
|
FINISHED |
| Object | advanced yeshiva 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: advanced yeshiva study | Statement: [dayan, trainingOftenIncludes, advanced yeshiva study]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainingOftenIncludes Context triple: [dayan, trainingOftenIncludes, advanced yeshiva study]
-
A.
trainingUnder
Indicates that one entity is receiving instruction, guidance, or mentorship from another, typically in a subordinate or apprentice-like capacity.
-
B.
trainingBase
Indicates that one entity serves as the training base, site, or facility where another entity receives training or instruction.
-
C.
training
Indicates that one entity is teaching, coaching, or otherwise helping another entity acquire or improve a skill, behavior, or capability.
-
D.
trainingClub
Indicates that one entity serves as a club or organization where the other entity receives training.
-
E.
typicalTraining
chosen
Indicates that an entity commonly undergoes or is associated with a standard or usual form of training in relation to another entity or context.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.