Triple
T25752254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chofetz Chaim Yeshiva |
E648495
|
entity |
| Predicate | studentBodyReligion |
P45
|
FINISHED |
| Object | Jewish |
—
|
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: Jewish | Statement: [Chofetz Chaim Yeshiva, studentBodyReligion, Jewish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studentBodyReligion Context triple: [Chofetz Chaim Yeshiva, studentBodyReligion, Jewish]
-
A.
religiousCampus
Indicates that a campus is affiliated with, governed by, or primarily dedicated to a particular religion or religious organization.
-
B.
religiousAffiliation
chosen
Indicates that one entity has a specified religious association, belief system, or denominational membership.
-
C.
associatedSchoolOfReligion
Indicates that an entity is connected with or belongs to a particular school or tradition within a religion.
-
D.
hostReligion
Indicates that an entity organizes, accommodates, or provides a venue for a particular religious group, event, or practice.
-
E.
governingReligionOfInstitution
Indicates that a particular religion serves as the official or primary religious affiliation guiding or overseeing an institution.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd7fe0908190904d919f24df7e97 |
completed | May 2, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 4:36 a.m.