Triple
T33899579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Scotland (1905) |
E869009
|
entity |
| Predicate | serviceStartPort |
P121932
|
FINISHED |
| Object | Vancouver |
—
|
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: Vancouver | Statement: [SS Empress of Scotland (1905), serviceStartPort, Vancouver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceStartPort Context triple: [SS Empress of Scotland (1905), serviceStartPort, Vancouver]
-
A.
routeStartPort
Indicates the port where a route or journey begins.
-
B.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
-
C.
serviceEntryPort
Indicates the port number through which a service is accessed or exposed for network communication.
-
D.
serviceStartLocation
chosen
Indicates the place where a service or operation is initiated or begins.
-
E.
registryPort
Indicates the network port number on which a registry service is exposed or accessed.
- 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_69fd02680d948190a3463fb119ba8556 |
completed | May 7, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69fcf89c69b4819082bbc564bd15137d |
completed | May 7, 2026, 8:39 p.m. |
Created at: May 1, 2026, 1:48 a.m.