Triple
T24451349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Coos Bay |
E616546
|
entity |
| Predicate | isDeepDraftPort |
P17158
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Port of Coos Bay, isDeepDraftPort, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDeepDraftPort Context triple: [Port of Coos Bay, isDeepDraftPort, true]
-
A.
isDeepWaterPort
chosen
Indicates that a port has sufficiently deep water to accommodate large, heavily loaded vessels without grounding.
-
B.
hasPortDepth
Indicates that a port possesses a specific water depth suitable for accommodating vessels.
-
C.
isDeepwaterPortTerminus
Indicates that a location serves as the endpoint or final stop of a transportation route at a deepwater port capable of accommodating large, ocean-going vessels.
-
D.
isMainDeepWaterPortFor
Indicates that one location serves as the primary deep-water port facility for another entity, such as a region, city, or country.
-
E.
isPortFor
Indicates that one entity serves as a port, interface, or connection point for another 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_69e2d7edca608190aafefc8877a1b4da |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298574dd48190813a7c82b7012600 |
completed | April 29, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:18 a.m.