Triple
T34000333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tierkidi refugee camp |
E871797
|
entity |
| Predicate | typeOfDisplacement |
P196185
|
FINISHED |
| Object | cross-border displacement |
—
|
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: cross-border displacement | Statement: [Tierkidi refugee camp, typeOfDisplacement, cross-border displacement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDisplacement Context triple: [Tierkidi refugee camp, typeOfDisplacement, cross-border displacement]
-
A.
displacementCategory
Indicates the type or classification of a displacement event or condition associated with an entity.
-
B.
displacement
Indicates a change in an entity’s position from one location to another, typically specifying both direction and magnitude of that movement.
-
C.
displacementOption
Indicates an available way or method by which something or someone can be moved, relocated, or shifted from one position or state to another.
-
D.
displacementCharacteristic
Indicates the nature or type of change in position or movement associated with an entity or interaction.
-
E.
hasDisplacementType
chosen
Indicates the specific kind or category of displacement associated with an entity or process.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a0117b6539c8190be7d231e891fe546 |
completed | May 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_6a011762f7ec8190afc884b92419d33f |
completed | May 10, 2026, 11:40 p.m. |
Created at: May 1, 2026, 1:50 a.m.