Triple
T3731948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lhotshampa |
E79084
|
entity |
| Predicate | migrationToBhutan |
P4275
|
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: [Lhotshampa, migrationToBhutan, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: migrationToBhutan Context triple: [Lhotshampa, migrationToBhutan, 19th century]
-
A.
migrationFrom
Indicates that an entity has moved, originated, or been transferred away from a specified source location or context.
-
B.
movedDomicileFromCountry
Indicates that an entity changed its place of residence from one specified country to another location.
-
C.
migrationBackground
Indicates that an entity has a personal or familial history of moving from one country or region to another, typically across national borders.
-
D.
historicalMigrationType
Indicates the type or category of migration that occurred in a historical context between entities.
-
E.
migration
chosen
Indicates the movement of entities from one location or context to another, often across boundaries or over time.
- 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_69ad8b0e4650819090ad7cef094285e8 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb21002c81908438170ed6f6c271 |
completed | March 8, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69adc04746588190b0dc535638f23546 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.