Triple
T36530853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Korean-Canadian |
E900438
|
entity |
| Predicate | typicalImmigrationOrigin |
P36274
|
FINISHED |
| Object | South Korea |
E3830
|
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: South Korea | Statement: [Korean-Canadian, typicalImmigrationOrigin, South Korea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalImmigrationOrigin Context triple: [Korean-Canadian, typicalImmigrationOrigin, South Korea]
-
A.
immigratesFrom
Indicates that an entity moves to live in a new country or region, originating from the specified source country or region.
-
B.
countryOfOriginForImmigration
chosen
Indicates the country from which a person or group has emigrated when moving to another country.
-
C.
immigrationDestinationFor
Indicates that a location serves as the destination to which an entity immigrates.
-
D.
hasImmigrantCommunitiesFrom
Indicates that a place or region contains established communities of people who have immigrated from a specified origin location.
-
E.
countryOfEmigration
Indicates the country from which a person or group has emigrated or moved away.
- 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_69f76e5fbb388190b70c4c15573c8143 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3a094999388190a430011d5c4bb8b7 |
completed | June 23, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_6a037a0bf4b88190bdcfae9a14b51f0a |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:11 p.m.