Triple
T30753683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vogelfluglinie |
E783021
|
entity |
| Predicate | seaCrossingSection |
P15424
|
FINISHED |
| Object | Puttgarden–Rødby 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: Puttgarden–Rødby ferry route | Statement: [Vogelfluglinie, seaCrossingSection, Puttgarden–Rødby ferry route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seaCrossingSection Context triple: [Vogelfluglinie, seaCrossingSection, Puttgarden–Rødby ferry route]
-
A.
waterwayTypeCrossed
Indicates the specific kind of waterway (e.g., river, canal, stream) that is being crossed in the described relationship or action.
-
B.
watercourseSectionOf
Indicates that a watercourse segment forms a constituent part of a larger watercourse.
-
C.
crossesWaterBody
chosen
Indicates that an entity moves from one side of a water body to the other by passing over, through, or across it.
-
D.
crossesWatershed
Indicates that one entity passes from one drainage basin or watershed area into another, traversing the boundary between them.
-
E.
lakeTypeCrossed
Indicates that one entity has traversed or passed across a lake of a specified type.
- 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_69f224af8d8481908bea03890c5618be |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f68f92c0448190a4c90ecfcbca0945 |
completed | May 2, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:39 p.m.