Triple
T24451361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Coos Bay |
E616546
|
entity |
| Predicate | railLineUse |
P33182
|
FINISHED |
| Object | freight |
—
|
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: freight | Statement: [Port of Coos Bay, railLineUse, freight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railLineUse Context triple: [Port of Coos Bay, railLineUse, freight]
-
A.
railwayLineUsage
chosen
Indicates how a railway line is used, such as the type or purpose of traffic or operations it supports.
-
B.
railwayUse
Indicates that something is used as, or functions in the capacity of, a railway or rail-based transportation facility.
-
C.
primaryRailUse
Indicates the main or predominant purpose for which a rail line, segment, or facility is used (e.g., passenger, freight, or mixed traffic).
-
D.
usesRailInfrastructureOf
Indicates that one entity operates on, accesses, or otherwise makes use of the rail infrastructure owned or managed by another entity.
-
E.
railLineOrigin
Indicates that a rail line begins or originates from a specified location or point.
- 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.