Triple
T32270970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazilian Jews |
E824412
|
entity |
| Predicate | KahalZurIsraelSynagogueLocation |
P84438
|
FINISHED |
| Object | Recife |
—
|
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: Recife | Statement: [Brazilian Jews, KahalZurIsraelSynagogueLocation, Recife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: KahalZurIsraelSynagogueLocation Context triple: [Brazilian Jews, KahalZurIsraelSynagogueLocation, Recife]
-
A.
synagogueName
Indicates that one entity is the name or designated title of a synagogue associated with another entity.
-
B.
mainSynagogue
chosen
Indicates that one entity serves as the primary or principal synagogue associated with another entity (such as a place, community, or organization).
-
C.
synagogueDate
Indicates the date associated with a synagogue, such as its construction, dedication, or another significant event in its history.
-
D.
hasSynagogueType
Indicates the specific classification or type of synagogue associated with an entity.
-
E.
builtSynagogue
Indicates that one entity constructed or was responsible for the building of a synagogue for another entity or community.
- 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc8766048190a663b878529d5450 |
completed | May 3, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:42 a.m.