Triple
T27369917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vordingborg |
E690284
|
entity |
| Predicate | connectsByBridgeTo |
P36619
|
FINISHED |
| Object | Masnedø |
—
|
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: Masnedø | Statement: [Vordingborg, connectsByBridgeTo, Masnedø]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsByBridgeTo Context triple: [Vordingborg, connectsByBridgeTo, Masnedø]
-
A.
bridgeConnectsVia
Indicates that a bridge serves as the connecting structure or route between two locations or entities via a specified path or medium.
-
B.
hasBridgeTo
chosen
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
C.
connectsTo
Indicates a relationship where one entity is linked or joined to another, allowing interaction, communication, or transfer between them.
-
D.
bridgesBetween
Indicates a relationship where something connects or links two otherwise separate entities, contexts, or states, enabling interaction or transition between them.
-
E.
plannedToBeConnectedTo
Indicates that one entity is intended or scheduled to be linked or joined with another entity in the future.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: April 27, 2026, 12:18 p.m.