Triple
T28361309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eastern Province (former) |
E718368
|
entity |
| Predicate | includedDistrict |
P22582
|
FINISHED |
| Object | Embu District |
—
|
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: Embu District | Statement: [Eastern Province (former), includedDistrict, Embu District]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedDistrict Context triple: [Eastern Province (former), includedDistrict, Embu District]
-
A.
includesDistrict
chosen
Indicates that one administrative or geographic entity contains or encompasses a specific district within its boundaries.
-
B.
containsDistrictMunicipality
Indicates that an administrative region includes one or more district municipalities within its boundaries.
-
C.
occursInDistrict
Indicates that an event or activity takes place within the boundaries of a specific district.
-
D.
hadDistrict
Indicates that an entity previously possessed, was associated with, or was administered by a particular district.
-
E.
hasDistrictPart
Indicates that one administrative or geographic entity includes another entity as a district-level subdivision or component.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: April 28, 2026, 12:52 a.m.