Triple
T28969691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonet |
E734236
|
entity |
| Predicate | proposedPortIntendedFor |
P175248
|
FINISHED |
| Object | trans-Pacific container shipping |
—
|
LITERAL 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: trans-Pacific container shipping | Statement: [Colonet, proposedPortIntendedFor, trans-Pacific container shipping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedPortIntendedFor Context triple: [Colonet, proposedPortIntendedFor, trans-Pacific container shipping]
-
A.
refersToPort
Indicates that one entity designates, points to, or is associated with a specific port (such as a network, hardware, or logical port).
-
B.
usedOnPort
Indicates that something is applied, connected, or operates specifically on a given port.
-
C.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
-
D.
usedInPort
Indicates that something is utilized or operates within a specific port.
-
E.
intendedNetwork
Indicates the network that an entity is planned, designed, or expected to connect to or operate within.
- F. None of above. chosen
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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 28, 2026, 9:04 a.m.