Triple
T33899580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Scotland (1905) |
E869009
|
entity |
| Predicate | serviceEndPort |
P26780
|
FINISHED |
| Object | Yokohama |
—
|
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: Yokohama | Statement: [SS Empress of Scotland (1905), serviceEndPort, Yokohama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceEndPort Context triple: [SS Empress of Scotland (1905), serviceEndPort, Yokohama]
-
A.
serviceEntryPort
Indicates the port number through which a service is accessed or exposed for network communication.
-
B.
serviceEnded
Indicates that a previously active service or service relationship has come to an end.
-
C.
serviceModuleDockingPort
Indicates a docking connection between a service module and a docking port.
-
D.
terminusPort
chosen
Indicates the port at which a route, journey, or connection ends or terminates.
-
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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: May 1, 2026, 1:48 a.m.