Triple
T32270974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazilian Jews |
E824412
|
entity |
| Predicate | mainImmigrationOrigins |
P70257
|
FINISHED |
| Object | Eastern Europe |
—
|
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: Eastern Europe | Statement: [Brazilian Jews, mainImmigrationOrigins, Eastern Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainImmigrationOrigins Context triple: [Brazilian Jews, mainImmigrationOrigins, Eastern Europe]
-
A.
countryOfOriginForImmigration
Indicates the country from which a person or group has emigrated when moving to another country.
-
B.
originalRefugeeOrigin
Indicates the place or country from which a refugee initially fled or was displaced.
-
C.
hasImmigrantCommunitiesFrom
chosen
Indicates that a place or region contains established communities of people who have immigrated from a specified origin location.
-
D.
immigrationBackground
Indicates that an entity has a personal or familial history of migration from another country or region.
-
E.
immigrationWaves
Indicates recurring or significant movements of people migrating into a place over time, often in large or distinct groups.
- 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_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:42 a.m.