Triple
T31866320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E45 |
E813464
|
entity |
| Predicate | crossesBodyOfWaterByFerry |
P152288
|
FINISHED |
| Object | Frederikshavn–Gothenburg ferry |
—
|
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: Frederikshavn–Gothenburg ferry | Statement: [E45, crossesBodyOfWaterByFerry, Frederikshavn–Gothenburg ferry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesBodyOfWaterByFerry Context triple: [E45, crossesBodyOfWaterByFerry, Frederikshavn–Gothenburg ferry]
-
A.
bodyOfWaterCrossedByFerry
chosen
Indicates that a body of water is traversed or crossed by a ferry service.
-
B.
hasFerryComponent
Indicates that something includes or is associated with a ferry-related part, feature, or segment within its structure or operation.
-
C.
requiresFerries
Indicates that traveling between two locations involves or depends on the use of one or more ferries.
-
D.
crossesWaterBody
Indicates that an entity moves from one side of a water body to the other by passing over, through, or across it.
-
E.
hasFerryService
Indicates that there is an operational ferry connection or transport service available between the related locations or entities.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 30, 2026, 11:54 p.m.