Triple
T31463045
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yaghnobi people |
E802654
|
entity |
| Predicate | resettlementDestination |
P108929
|
FINISHED |
| Object | Zafarabad District |
—
|
NE NERFINISHED |
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: Zafarabad District | Statement: [Yaghnobi people, resettlementDestination, Zafarabad District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resettlementDestination Context triple: [Yaghnobi people, resettlementDestination, Zafarabad District]
-
A.
resettledBy
Indicates that an entity has been moved or established anew in a location or context by another agent or authority.
-
B.
resettlementStatus
Indicates the current stage or condition of an entity’s relocation or re-establishment process in a new place.
-
C.
resettledAt
chosen
Indicates that an entity has moved and established residence or presence at a new location.
-
D.
purposeOfResettlement
Indicates that one entity’s purpose, goal, or intended outcome is the reason or motivation for another entity’s act of resettling or being resettled.
-
E.
majorResettlementArea
Indicates that a location serves as a primary or significant destination area where people are being resettled.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:21 p.m.