Triple
T11361352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Thais |
E269092
|
entity |
| Predicate | historicalMigrationPeak |
P4936
|
FINISHED |
| Object | late 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: late 19th century | Statement: [Chinese Thais, historicalMigrationPeak, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalMigrationPeak Context triple: [Chinese Thais, historicalMigrationPeak, late 19th century]
-
A.
historicalPopulationMovement
Indicates the movement or migration of a population from one place to another during a specific historical period or event.
-
B.
historicalMigrationType
Indicates the type or category of migration that occurred in a historical context between entities.
-
C.
populationAtPeak
Indicates that an entity’s population size is measured at its highest recorded level during a specified time or condition.
-
D.
historicalPeak
chosen
Indicates that the related value or state represents the highest level ever reached by something within a historical or recorded time frame.
-
E.
historicalMigrationFactor
Indicates that the relationship or condition is influenced by patterns, causes, or consequences of past human migration.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e7022d508190996f9be0847c2b41 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.