Triple
T32033829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sephardic Jewish community of Newport |
E818038
|
entity |
| Predicate | builtSynagogue |
P173499
|
FINISHED |
| Object | Touro Synagogue |
—
|
NE NERFINISHED |
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: Touro Synagogue | Statement: [Sephardic Jewish community of Newport, builtSynagogue, Touro Synagogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtSynagogue Context triple: [Sephardic Jewish community of Newport, builtSynagogue, Touro Synagogue]
-
A.
mainSynagogue
Indicates that one entity serves as the primary or principal synagogue associated with another entity (such as a place, community, or organization).
-
B.
hasSynagogueType
Indicates the specific classification or type of synagogue associated with an entity.
-
C.
synagogueName
Indicates that one entity is the name or designated title of a synagogue associated with another entity.
-
D.
synagogueDate
Indicates the date associated with a synagogue, such as its construction, dedication, or another significant event in its history.
-
E.
hasHistoricSynagogueBuilding
Indicates that an entity possesses or is associated with a synagogue building of historic significance.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b56ed31481908c3e5d749e46bad9 |
completed | May 3, 2026, 2:39 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
| PDg | Predicate description generation | batch_69f6b49339048190b617a6749f648825 |
completed | May 3, 2026, 2:36 a.m. |
Created at: May 1, 2026, 12:18 a.m.