Triple
T32270994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brazilian Jews |
E824412
|
entity |
| Predicate | commonMigrationDestination |
P137161
|
FINISHED |
| Object | Israel |
—
|
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: Israel | Statement: [Brazilian Jews, commonMigrationDestination, Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonMigrationDestination Context triple: [Brazilian Jews, commonMigrationDestination, Israel]
-
A.
notableMigrationDestination
chosen
Indicates that a place is a significant or well-known destination to which people migrate from other locations.
-
B.
creatorMigrationDestination
Indicates the location or entity to which a creator moves or relocates as part of a migration process.
-
C.
migrationFrom
Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
-
D.
supportsMigrationOf
Indicates that one entity enables, facilitates, or is compatible with the migration or transfer of another entity from one environment, system, or context to another.
-
E.
migration
Indicates the movement of entities from one location or context to another, often across boundaries or over time.
- 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_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: May 1, 2026, 12:42 a.m.