Triple
T21943062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sze Yup region |
E541868
|
entity |
| Predicate | majorEmigrationPeriod |
P80942
|
FINISHED |
| Object | 19th century |
—
|
LITERAL 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: 19th century | Statement: [Sze Yup region, majorEmigrationPeriod, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorEmigrationPeriod Context triple: [Sze Yup region, majorEmigrationPeriod, 19th century]
-
A.
majorImmigrationPeriod
Indicates that a time interval represents a significant period during which substantial immigration occurred.
-
B.
majorImmigrationWaveFrom
Indicates that a significant, large-scale movement of immigrants originated from one place and arrived in another.
-
C.
centuryOfMajorMigration
chosen
Indicates the century during which a major migration event involving the entity took place.
-
D.
hasSignificantEmigrationTo
Indicates that a substantial number of people leave one place, group, or entity to move and settle in another specific place, group, or entity.
-
E.
historicalPopulationMovement
Indicates the movement or migration of a population from one place to another during a specific historical period or event.
- 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_69e0c47e2e5c81909a7f74ce3de50911 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1242515ec8190b015bf8c7b13be85 |
completed | April 28, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 7:56 p.m.