Triple
T34184102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stony Athi River |
E876908
|
entity |
| Predicate | hasToponymElement |
P96333
|
FINISHED |
| Object | Athi |
—
|
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 | Statement: [Stony Athi River, hasToponymElement, Athi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasToponymElement Context triple: [Stony Athi River, hasToponymElement, Athi]
-
A.
hasTypeOfToponym
Indicates that one entity is classified as a specific type or category of toponym (place name) in relation to another entity.
-
B.
hasToponymicFeature
Indicates that an entity is associated with or characterized by a specific geographic or place-related feature (toponym).
-
C.
hasToponymy
Indicates a relationship where one entity possesses or is associated with the system, study, or set of place names (toponyms) of another entity.
-
D.
toponymyContainsElement
chosen
Indicates that a toponym (place name) includes a specific linguistic or semantic element as part of its composition.
-
E.
includesToponym
Indicates that one entity contains or references a place name (toponym) associated with another entity.
- 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_69f349ae640c8190b9cd220b5368d8b6 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 1, 2026, 1:55 a.m.