Triple
T5361580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salar |
E103032
|
entity |
| Predicate | historicalMigrationRoute |
P19590
|
FINISHED |
| Object | from Central Asia to Qinghai |
—
|
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: from Central Asia to Qinghai | Statement: [Salar, historicalMigrationRoute, from Central Asia to Qinghai]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalMigrationRoute Context triple: [Salar, historicalMigrationRoute, from Central Asia to Qinghai]
-
A.
historicalMigrationType
Indicates the type or category of migration that occurred in a historical context between entities.
-
B.
historicalPopulationMovement
chosen
Indicates the movement or migration of a population from one place to another during a specific historical period or event.
-
C.
historicRoute
Indicates that a route has historical significance, typically due to its age, past usage, or role in notable events.
-
D.
historicallyNomadic
Indicates that an entity has traditionally led a mobile, wandering lifestyle without permanent settlement over a significant historical period.
-
E.
directionOfMigration
Indicates the geographic direction or path along which a migration movement proceeds from its origin toward its destination.
- 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_69bd43daa3e4819090b59d127db70e57 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd865a0bb081909579cfe7c7974075 |
completed | March 20, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69bd845f41f88190b75b8b64b9e41862 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:02 p.m.