Triple
T34000331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tierkidi refugee camp |
E871797
|
entity |
| Predicate | refugeeStatusGuidedBy |
P47430
|
FINISHED |
| Object | UNHCR mandate |
—
|
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: UNHCR mandate | Statement: [Tierkidi refugee camp, refugeeStatusGuidedBy, UNHCR mandate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refugeeStatusGuidedBy Context triple: [Tierkidi refugee camp, refugeeStatusGuidedBy, UNHCR mandate]
-
A.
hasRefugeeStatusRecognizedBy
chosen
Indicates that an entity’s refugee status has been formally recognized or granted by a specified authority or organization.
-
B.
wasRefugee
Indicates that an entity previously lived as a refugee, having been forced to leave their home country due to conflict, persecution, or disaster.
-
C.
refugeeAdministration
Indicates the management, coordination, or oversight of services, policies, and procedures related to refugees.
-
D.
designatedAsRefuge
Indicates that an entity has been officially assigned or recognized as a refuge or place of protection.
-
E.
resettlementStatus
Indicates the current stage or condition of an entity’s relocation or re-establishment process in a new place.
- 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_69f70fb4f18c819099ef6d9177b7d205 |
completed | May 3, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69f70f3a54d481909ba6bdda3647b761 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:50 a.m.