Triple
T34000324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tierkidi refugee camp |
E871797
|
entity |
| Predicate | hostCommunityRegion |
P79811
|
FINISHED |
| Object | Gambela regional state |
—
|
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: Gambela regional state | Statement: [Tierkidi refugee camp, hostCommunityRegion, Gambela regional state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCommunityRegion Context triple: [Tierkidi refugee camp, hostCommunityRegion, Gambela regional state]
-
A.
hostsCommunity
Indicates that an entity organizes or provides a venue for a community or community-related activities.
-
B.
networkRegion
Indicates that an entity belongs to, operates within, or is associated with a specific network-defined geographic or logical region.
-
C.
mainHostRegion
Indicates the primary geographic or network region in which a host or hosting environment is located or operates.
-
D.
hubTerritory
Indicates that a given territory functions as a central hub or primary focal area within a broader geographic or organizational structure.
-
E.
typicalHostRegion
chosen
Indicates the geographic region where a host is most commonly or characteristically found or associated.
- 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_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:50 a.m.