Triple
T21943114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Counties area of Guangdong |
E541869
|
entity |
| Predicate | migrationPeak |
P96261
|
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: [Four Counties area of Guangdong, migrationPeak, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: migrationPeak Context triple: [Four Counties area of Guangdong, migrationPeak, 19th century]
-
A.
migration
Indicates the movement of entities from one location or context to another, often across boundaries or over time.
-
B.
migrationTiming
chosen
Indicates the temporal characteristics or schedule of when a migration event occurs or is expected to occur.
-
C.
migrationEvent
Indicates an event in which one or more entities move or relocate from one place or context to another, typically across defined boundaries or regions.
-
D.
migrationFrom
Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
-
E.
migrationBackground
Indicates that an entity has a personal or familial history of moving from one country or region to another, typically across national borders.
- 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.