Triple
T32714276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabaki |
E836477
|
entity |
| Predicate | isMainUrbanCentreNear |
P36605
|
FINISHED |
| Object | Athi River settlements |
—
|
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: Athi River settlements | Statement: [Sabaki, isMainUrbanCentreNear, Athi River settlements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMainUrbanCentreNear Context triple: [Sabaki, isMainUrbanCentreNear, Athi River settlements]
-
A.
connectsToUrbanCenter
Indicates that one entity has a direct or functional linkage to an urban center, such as through infrastructure, services, or regular interaction.
-
B.
nearbyUrbanCenter
chosen
Indicates that one location is geographically close to an urban center, such as a city or large town.
-
C.
isNearCapitalCity
Indicates that an entity is located close to, or in the immediate vicinity of, a capital city.
-
D.
hasUrbanProximity
Indicates that one entity is located near or within easy access to an urban area associated with another entity.
-
E.
isUrbanCentreFor
Indicates that one place functions as the primary urban hub or central city serving another area or population.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:11 a.m.