Triple
T22339890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam Central Station ferry terminal |
E552244
|
entity |
| Predicate | hasRoute |
P4374
|
FINISHED |
| Object | F6 ferry route |
—
|
NE NERFINISHED |
How this triple was built (3 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: F6 ferry route | Statement: [Amsterdam Central Station ferry terminal, hasRoute, F6 ferry route]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: F6 ferry route Context triple: [Amsterdam Central Station ferry terminal, hasRoute, F6 ferry route]
-
A.
F3 ferry route
The F3 ferry route is a public passenger ferry service in Amsterdam that connects Amsterdam Central Station with destinations across the IJ waterway as part of the city’s urban transport network.
-
B.
Horseshoe Bay–Langdale ferry route
The Horseshoe Bay–Langdale ferry route is a major BC Ferries connection linking Metro Vancouver to British Columbia’s Sunshine Coast across Howe Sound.
-
C.
Glenora Ferry route
The Glenora Ferry route is a free car and passenger ferry service that crosses the Bay of Quinte in Ontario, connecting Prince Edward County with the mainland as part of Highway 33 (Loyalist Parkway).
-
D.
Metlink Ferry
Metlink Ferry is the branded passenger ferry service operating as part of the Metlink public transport network in the Wellington region of New Zealand.
-
E.
Earls Cove–Saltery Bay ferry route
The Earls Cove–Saltery Bay ferry route is a coastal British Columbia ferry service that connects the two segments of the Sunshine Coast highway corridor across Jervis Inlet.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: F6 ferry route Target entity description: The F6 ferry route is a public passenger ferry service in Amsterdam that connects Amsterdam Central Station with destinations across the IJ waterway as part of the city’s urban transport network.
-
A.
F3 ferry route
The F3 ferry route is a public passenger ferry service in Amsterdam that connects Amsterdam Central Station with destinations across the IJ waterway as part of the city’s urban transport network.
-
B.
Horseshoe Bay–Langdale ferry route
The Horseshoe Bay–Langdale ferry route is a major BC Ferries connection linking Metro Vancouver to British Columbia’s Sunshine Coast across Howe Sound.
-
C.
Glenora Ferry route
The Glenora Ferry route is a free car and passenger ferry service that crosses the Bay of Quinte in Ontario, connecting Prince Edward County with the mainland as part of Highway 33 (Loyalist Parkway).
-
D.
Metlink Ferry
Metlink Ferry is the branded passenger ferry service operating as part of the Metlink public transport network in the Wellington region of New Zealand.
-
E.
Earls Cove–Saltery Bay ferry route
The Earls Cove–Saltery Bay ferry route is a coastal British Columbia ferry service that connects the two segments of the Sunshine Coast highway corridor across Jervis Inlet.
- F. None of above. chosen
Provenance (2 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157824f588190882bea9e61dd5a83 |
completed | April 29, 2026, 12:57 a.m. |
Created at: April 16, 2026, 8:43 p.m.