Triple
T25699512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nairobi–Dar es Salaam |
E644417
|
entity |
| Predicate | connectsCommercialHubOf |
P111188
|
FINISHED |
| Object | Tanzania |
—
|
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: Tanzania | Statement: [Nairobi–Dar es Salaam, connectsCommercialHubOf, Tanzania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsCommercialHubOf Context triple: [Nairobi–Dar es Salaam, connectsCommercialHubOf, Tanzania]
-
A.
connectsCommercialAreas
Indicates a relationship where one entity links or provides direct access between two or more commercial areas or business districts.
-
B.
isCommercialHubIn
Indicates that a place functions as a primary center of commercial or business activity within a specified larger area or region.
-
C.
isCentralHubOf
Indicates that one entity functions as the primary connecting or coordinating hub for activities, resources, or interactions among multiple other entities.
-
D.
connectsMajorHub
chosen
Indicates that one entity serves as a link or route between major hubs or primary nodes in a network.
-
E.
connectsWorks
Indicates a relationship where one work serves to link, bridge, or associate two or more other works.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 21, 2026, 8:42 p.m.