Triple
T31962486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schleswig harbor |
E816079
|
entity |
| Predicate | locatedInInlet |
—
|
GENERATED |
| Object | Schlei inlet |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInInlet Context triple: [Schleswig harbor, locatedInInlet, Schlei inlet]
-
A.
locatedAtOutletOf
Indicates that one entity is positioned at or directly adjacent to the outlet or discharge point of another entity (such as a flow, channel, or system).
-
B.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
locatedInTheInteriorOf
Indicates that one entity is situated entirely within the inner part or inside area of another entity, rather than on its surface or boundary.
-
D.
intakeLocation
Indicates the place or facility where an entity is initially received, admitted, or taken in.
-
E.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
- F. None of above.
Provenance (1 batch)
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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:09 a.m.