Triple
T35750918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E67 |
E1033317
|
entity |
| Predicate | connectsByFerry |
P1831
|
FINISHED |
| Object | Tallinn–Helsinki ferry route |
—
|
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: Tallinn–Helsinki ferry route | Statement: [European route E67, connectsByFerry, Tallinn–Helsinki ferry route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsByFerry Context triple: [European route E67, connectsByFerry, Tallinn–Helsinki ferry route]
-
A.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
-
B.
linkedByFerryTo
chosen
Indicates that one place is connected to another by a ferry route that enables transport between them.
-
C.
requiresFerries
Indicates that traveling between two locations involves or depends on the use of one or more ferries.
-
D.
travelTimeByFerry
Indicates the duration required to travel between two locations specifically using a ferry as the mode of transportation.
-
E.
bodyOfWaterCrossedByFerry
Indicates that a body of water is traversed or crossed by a ferry service.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff965f9be48190b015b788207be676 |
completed | May 9, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69ff95d3015c8190b9d293fe31b859c3 |
completed | May 9, 2026, 8:15 p.m. |
Created at: May 3, 2026, 4:06 p.m.