Triple
T30402269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nairobi Expressway |
E773379
|
entity |
| Predicate | concessionPeriod |
P52215
|
FINISHED |
| Object | about 27 years |
—
|
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: about 27 years | Statement: [Nairobi Expressway, concessionPeriod, about 27 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concessionPeriod Context triple: [Nairobi Expressway, concessionPeriod, about 27 years]
-
A.
concessionDuration
chosen
Indicates the length of time for which a concession, such as a granted right or privilege, remains valid or in effect between parties.
-
B.
concessionExpiry
Indicates that a granted concession or special permission remains valid only until a specified expiration time or date.
-
C.
concessionDate
Indicates the date on which a concession, such as a right, license, or contract, is formally granted or comes into effect.
-
D.
concessionYear
Indicates the year in which a concession, such as a right, license, or contract, was formally granted or came into effect.
-
E.
concessionType
Indicates the specific kind or category of concession (such as a discount, exemption, or special allowance) that applies in a given context.
- 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_69f2248facd48190b183c3f3ca6daef7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f727afd5d88190ad48735cd1b32787 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72737c42c8190a3f781a5e98868ff |
completed | May 3, 2026, 10:45 a.m. |
Created at: April 29, 2026, 8:03 p.m.