Triple
T21815926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schechter Rabbinical Seminary |
E538605
|
entity |
| Predicate | servesCommunitiesWorldwide |
P145773
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Schechter Rabbinical Seminary, servesCommunitiesWorldwide, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesCommunitiesWorldwide Context triple: [Schechter Rabbinical Seminary, servesCommunitiesWorldwide, true]
-
A.
servesNearbyCommunities
Indicates that an entity provides services or support to communities located in its surrounding area.
-
B.
servesCommunitiesAlong
Indicates that something provides services or support to the communities located along a particular route, corridor, or area.
-
C.
servesCommunityDescribedAs
Indicates that an entity provides services or support to a community characterized or described in a particular way.
-
D.
hasCountryServed
Indicates that a person or organization has provided service to, or performed duties on behalf of, a specified country.
-
E.
usedWorldwide
Indicates that something is utilized or applied across many countries or regions around the world.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07ccac9f08190b835ee7a40ecf4c2 |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c670ee608190b9cfdc09de74f0de |
completed | April 21, 2026, 12:36 a.m. |
Created at: April 16, 2026, 6:54 p.m.