Triple
T30753685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vogelfluglinie |
E783021
|
entity |
| Predicate | plannedSuccessorProject |
P74594
|
FINISHED |
| Object | Fehmarnbelt Tunnel |
—
|
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: Fehmarnbelt Tunnel | Statement: [Vogelfluglinie, plannedSuccessorProject, Fehmarnbelt Tunnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedSuccessorProject Context triple: [Vogelfluglinie, plannedSuccessorProject, Fehmarnbelt Tunnel]
-
A.
successorProject
chosen
Indicates that one project directly follows and continues or replaces another project in sequence.
-
B.
successorProjectHolder
Indicates that one entity is the project holder that directly succeeds another in a sequence or lifecycle of project ownership.
-
C.
successorProjectNumber
Indicates that one project’s identifying number directly follows and replaces another project’s number in a sequence or lifecycle.
-
D.
predecessorProject
Indicates that one project temporally or logically comes before and leads into another project in a sequence or dependency chain.
-
E.
successorPlannedName
Indicates that a new name has been planned to replace or succeed the current name.
- 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_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
Created at: April 29, 2026, 8:39 p.m.