Triple
T31962486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schleswig harbor |
E816079
|
entity |
| Predicate | locatedInInlet |
P40
|
FINISHED |
| Object | Schlei inlet |
E802819
|
NE FINISHED |
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: Schlei inlet | Statement: [Schleswig harbor, locatedInInlet, Schlei inlet]
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 (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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a01e3a2d0e08190a7d5622920dc56e6 |
completed | May 11, 2026, 2:11 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eddcf3e7c8190a5a30c44ca30d968 |
completed | June 14, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_6a01e3013e7881909f0cdca25a53c009 |
completed | May 11, 2026, 2:09 p.m. |
Created at: May 1, 2026, 12:09 a.m.