Triple
T13038200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirinyaga |
E326618
|
entity |
| Predicate | reveredSince |
P66044
|
FINISHED |
| Object | pre-colonial period |
—
|
LITERAL FINISHED |
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: pre-colonial period | Statement: [Kirinyaga, reveredSince, pre-colonial period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reveredSince Context triple: [Kirinyaga, reveredSince, pre-colonial period]
-
A.
celebratedAfter
Indicates that one event or celebration occurs later in time as a result of, or in response to, another specified event.
-
B.
commemoratedSince
chosen
Indicates that a commemoration of one entity for another has been in effect starting from a specific point in time.
-
C.
celebratedSinceCentury
Indicates that a celebration, commemoration, or observance of something has been taking place continuously since a specified century.
-
D.
enshrinedSince
Indicates that something has been formally established, preserved, or honored starting from a specific point in time.
-
E.
representedSince
Indicates that one entity has been acting as a representative or agent for another entity continuously from a specified starting time.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98a9829b48190b23624b6b3df4600 |
completed | April 10, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69d9803aca4c8190b1015cd159cc47a9 |
completed | April 10, 2026, 10:56 p.m. |
Created at: April 9, 2026, 8:55 p.m.