Triple
T24409672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific Coast Steamship Company |
E615412
|
entity |
| Predicate | operatedPort |
P30654
|
FINISHED |
| Object | San Francisco |
—
|
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: San Francisco | Statement: [Pacific Coast Steamship Company, operatedPort, San Francisco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedPort Context triple: [Pacific Coast Steamship Company, operatedPort, San Francisco]
-
A.
portTypeOperated
Indicates that one entity operates, manages, or runs the specified type of port associated with another entity.
-
B.
hasPortOperator
chosen
Indicates that a port is operated, managed, or run by a specific port operator entity.
-
C.
controlledPort
Indicates that one entity has authority over or manages the operation or configuration of a specific port of another entity.
-
D.
operatedPortionsOf
Indicates that an agent has performed operational control or management over specific parts or segments of a larger system, asset, or entity.
-
E.
connectionPort
Indicates a specific port through which two components, systems, or devices are connected or can communicate.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2958076a88190880feb3ea6c0abf1 |
completed | April 29, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:05 a.m.