Triple
T31936291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TRC |
E815395
|
entity |
| Predicate | operatesPortAccess |
P30654
|
FINISHED |
| Object | Port of Dar es Salaam |
—
|
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: Port of Dar es Salaam | Statement: [TRC, operatesPortAccess, Port of Dar es Salaam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesPortAccess Context triple: [TRC, operatesPortAccess, Port of Dar es Salaam]
-
A.
portTypeOperated
Indicates that one entity operates, manages, or runs the specified type of port associated with another entity.
-
B.
hasNearbyPortAccess
Indicates that an entity is located close enough to a port to feasibly use it for access or transport.
-
C.
controlledPort
Indicates that one entity has authority over or manages the operation or configuration of a specific port of another entity.
-
D.
portActivity
Indicates the level or type of operational activity occurring at a port, such as ship movements, cargo handling, or related maritime operations.
-
E.
hasPortOperator
chosen
Indicates that a port is operated, managed, or run by a specific port operator 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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ffe6e2eb688190a45fd2c6415cd86a |
completed | May 10, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69ffe65939488190a35b9c2e9c7ad868 |
completed | May 10, 2026, 1:58 a.m. |
Created at: May 1, 2026, 12:05 a.m.