Triple
T16045910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N25 road |
E389217
|
entity |
| Predicate | connectsToFerryRoutes |
P1737
|
FINISHED |
| Object | ferry services to the United Kingdom |
—
|
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: ferry services to the United Kingdom | Statement: [N25 road, connectsToFerryRoutes, ferry services to the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToFerryRoutes Context triple: [N25 road, connectsToFerryRoutes, ferry services to the United Kingdom]
-
A.
isOneOfMainCarFerryRoutesTo
Indicates that something serves as one of the primary car ferry routes leading to a specified destination.
-
B.
hasNearbyFerryRoute
Indicates that there is a ferry route located close to the referenced entity.
-
C.
hasFerryService
chosen
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
D.
hasFerryComponent
Indicates that something includes or is associated with a ferry-related part, feature, or segment within its structure or operation.
-
E.
hasFerryType
Indicates that an entity (such as a ferry route or service) is associated with a specific type or category of ferry.
- 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_69d86dae698881908327ef2d67706cb9 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.