Triple
T33996087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falash Mura |
E871676
|
entity |
| Predicate | hasNotableMigrationDestination |
P137161
|
FINISHED |
| Object | Israel |
E6036
|
NE 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: Israel | Statement: [Falash Mura, hasNotableMigrationDestination, Israel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableMigrationDestination Context triple: [Falash Mura, hasNotableMigrationDestination, Israel]
-
A.
notableMigrationDestination
chosen
Indicates that a place is a significant or well-known destination to which people migrate from other locations.
-
B.
hasReasonForMigration
Indicates that there exists a specific cause, motive, or justification for an entity’s act of migrating from one place to another.
-
C.
hasMigrationTo
Indicates a directed movement or transfer from one place, system, or state to another.
-
D.
hasMigrationIssue
Indicates that an entity experiences a problem, error, or complication during a migration process from one system, environment, or version to another.
-
E.
hasMigrationHistoryFrom
Indicates that an entity has a recorded history of migrating or moving from a specified origin location or source.
- F. None of above.
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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0245e917748190bf0a65db538aa66f |
completed | May 11, 2026, 9:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a36c1ab5fa8819080ea30f31c96c999 |
completed | June 20, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_6a023f7cf7148190af5c2ea501511145 |
completed | May 11, 2026, 8:43 p.m. |
Created at: May 1, 2026, 1:50 a.m.