Triple
T25752232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chofetz Chaim Yeshiva |
E648495
|
entity |
| Predicate | locatedInTheHistoricRegion |
P88079
|
FINISHED |
| Object | Radin |
E149399
|
NE 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: Radin | Statement: [Chofetz Chaim Yeshiva, locatedInTheHistoricRegion, Radin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTheHistoricRegion Context triple: [Chofetz Chaim Yeshiva, locatedInTheHistoricRegion, Radin]
-
A.
locatedInHistoricSite
Indicates that an entity is situated within or on the grounds of a place officially recognized as a historic site.
-
B.
partOfHistoricalArea
Indicates that one entity is located within or belongs to a designated historical area or heritage zone.
-
C.
locatedInProvinceHistorical
Indicates that an entity was situated within a specific province during a historical period or according to historical administrative boundaries.
-
D.
locatedInModernAdministrativeRegion
Indicates that an entity is geographically situated within the boundaries of a current, officially recognized administrative region.
-
E.
locatedInTraditionalRegion
chosen
Indicates that an entity is situated within a specific traditional or historically recognized region.
- F. None of above.
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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10cc1095f081908a9c722e059d834a |
completed | May 22, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 22, 2026, 4:36 a.m.