Triple
T3731961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lhotshampa |
E79084
|
entity |
| Predicate | resettlementProgram |
P11175
|
FINISHED |
| Object | third-country resettlement from Nepal |
—
|
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: third-country resettlement from Nepal | Statement: [Lhotshampa, resettlementProgram, third-country resettlement from Nepal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resettlementProgram Context triple: [Lhotshampa, resettlementProgram, third-country resettlement from Nepal]
-
A.
majorResettlementArea
Indicates that a location serves as a primary or significant destination area where people are being resettled.
-
B.
refugeeAdministration
Indicates the management, coordination, or oversight of services, policies, and procedures related to refugees.
-
C.
reconstructedWithAidProgram
Indicates that an entity was rebuilt or restored through the support or resources provided by an aid program.
-
D.
settledAfterDeportationIn
Indicates that an entity established residence in a place following its deportation or forced removal.
-
E.
relocated
chosen
Indicates that an entity has moved or been moved from one location or position to another.
- 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.