Triple
T29572008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rendsburg Loop |
E753338
|
entity |
| Predicate | crossesViaAdjacentBridge |
P177565
|
FINISHED |
| Object | Kiel Canal |
—
|
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: Kiel Canal | Statement: [Rendsburg Loop, crossesViaAdjacentBridge, Kiel Canal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesViaAdjacentBridge Context triple: [Rendsburg Loop, crossesViaAdjacentBridge, Kiel Canal]
-
A.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
-
B.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
C.
hasBridgeCrossings
Indicates that one entity has one or more bridge structures that span across or connect over another entity (such as a road, river, or area).
-
D.
crossesTo
Indicates that one entity moves or extends from one side or area to another, passing over or through some boundary or intervening space.
-
E.
crossesBetween
Indicates that one entity passes from one side of a second entity to the other, traversing the space between two reference points or boundaries associated with that second entity.
- F. None of above. chosen
Provenance (4 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_69f0ef7fcb4881908a933110adb9bda1 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 28, 2026, 5:59 p.m.