Triple
T25447332
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EASTAFRICAN |
E637671
|
entity |
| Predicate | operatedByRegion |
P179895
|
FINISHED |
| Object | East Africa |
—
|
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: East Africa | Statement: [EASTAFRICAN, operatedByRegion, East Africa]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedByRegion Context triple: [EASTAFRICAN, operatedByRegion, East Africa]
-
A.
operatedInRegion
Indicates that an entity conducted operations or activities within a specified geographic region.
-
B.
operatesToRegion
Indicates that an agent conducts operations or provides services directed toward or within a specified region.
-
C.
operatedByCountry
Indicates that an entity (such as an organization, facility, or service) is run, managed, or controlled by a specific country or its government.
-
D.
operatesBetweenRegion
Indicates a relationship in which an entity conducts operations or provides services that connect or span between two distinct regions.
-
E.
operatesBrandInRegion
Indicates that an entity manages or runs a specific brand within a particular geographic region.
- F. None of above. chosen
Provenance (4 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_69e75db7c5048190b8da9cd7eeedb610 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
| PDg | Predicate description generation | batch_69f72920c6208190aa4aba6cb6193109 |
completed | May 3, 2026, 10:53 a.m. |
Created at: April 21, 2026, 2:02 p.m.