Triple
T31936228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Railway line |
E815393
|
entity |
| Predicate | primaryPortServed |
P185623
|
FINISHED |
| Object | Port of Dar es Salaam |
E475393
|
NE 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: Port of Dar es Salaam | Statement: [Central Railway line, primaryPortServed, Port of Dar es Salaam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPortServed Context triple: [Central Railway line, primaryPortServed, Port of Dar es Salaam]
-
A.
servedByPort
chosen
Indicates that something (such as a service, route, or connection) is provided or made accessible through a particular port.
-
B.
primaryCorridorServed
Indicates that a corridor is the main route or pathway served by a given service, facility, or entity.
-
C.
primaryServes
Indicates that one entity’s main or principal function is to serve, support, or provide service to another entity.
-
D.
nearbyPortsServed
Indicates that a location is served or supported by one or more ports situated in its nearby geographic vicinity.
-
E.
primaryHubFor
Indicates that one entity serves as the main central hub or core point of coordination for another entity or set of entities.
- F. None of above.
Provenance (4 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e8a3f56a08190b5fe26e362aa0d03 |
completed | June 14, 2026, 11:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:05 a.m.