Triple
T28513627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uduk |
E721556
|
entity |
| Predicate | refugeeExperience |
P106206
|
FINISHED |
| Object | many sought refuge in Ethiopia |
—
|
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: many sought refuge in Ethiopia | Statement: [Uduk, refugeeExperience, many sought refuge in Ethiopia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refugeeExperience Context triple: [Uduk, refugeeExperience, many sought refuge in Ethiopia]
-
A.
wasRefugee
Indicates that an entity previously lived as a refugee, having been forced to leave their home country due to conflict, persecution, or disaster.
-
B.
contextOfRefugees
chosen
Indicates the situational, social, or environmental circumstances in which refugees exist or to which they are related.
-
C.
refugeeParticipation
Indicates that refugees are actively involved in, contribute to, or take part in a specific activity, process, program, or decision-making context.
-
D.
refugeeOriginEvent
Indicates an event or circumstance that caused or is associated with a person or group becoming refugees and leaving their place of origin.
-
E.
nearRefugeeCamp
Indicates that one entity is located in close physical proximity to a refugee camp.
- 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64f77c86c8190bb05cffae7c17a00 |
completed | May 2, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 3:14 a.m.