Triple
T38173236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Companhia das Docas do Estado da Bahia |
E1000134
|
entity |
| Predicate | hasPortInNetwork |
P181402
|
FINISHED |
| Object | Port of Salvador |
—
|
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 Salvador | Statement: [Companhia das Docas do Estado da Bahia, hasPortInNetwork, Port of Salvador]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPortInNetwork Context triple: [Companhia das Docas do Estado da Bahia, hasPortInNetwork, Port of Salvador]
-
A.
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).
-
B.
isInPort
Indicates that an entity (such as a vessel or vehicle) is currently located within or docked at a specific port.
-
C.
hasPortRole
Indicates that an entity participates in a port with a specified functional or operational role.
-
D.
hasPorts
Indicates that an entity is equipped with or provides access points (ports) for connection, communication, or interface with other entities or systems.
-
E.
belongsToPortNetwork
chosen
Indicates that something is a member of, or associated with, a specific port network.
- 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_69f76daaace48190a38cee37f8ce343f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a000be59ad88190a6aa3a42c097796d |
completed | May 10, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_6a000ab6e9bc81908300b81d004e5921 |
completed | May 10, 2026, 4:33 a.m. |
Created at: May 3, 2026, 4:29 p.m.