Triple
T25275877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South African ports |
E633693
|
entity |
| Predicate | includePort |
P65472
|
FINISHED |
| Object | Port of Durban |
—
|
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 Durban | Statement: [South African ports, includePort, Port of Durban]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includePort Context triple: [South African ports, includePort, Port of Durban]
-
A.
includesPort
chosen
Indicates that one entity contains, encompasses, or has as part of it a specific port or set of ports.
-
B.
supportsPort
Indicates that one entity is capable of handling, providing, or being compatible with a specified port or port configuration.
-
C.
includesAPI
Indicates that one entity provides or contains an application programming interface (API) that can be used by another entity.
-
D.
hasPortUse
Indicates that one entity utilizes or is assigned to a particular port for access, communication, or operation.
-
E.
hasPortOn
Indicates that one entity possesses or is located adjacent to a port situated on another specified geographic or infrastructural feature (such as a coast, river, or lake).
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 21, 2026, 1:17 p.m.