Triple
T19650835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Södertälje |
E471808
|
entity |
| Predicate | waterway |
P1778
|
FINISHED |
| Object | Södertälje lock |
—
|
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: Södertälje lock | Statement: [Södertälje, waterway, Södertälje lock]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Södertälje lock Context triple: [Södertälje, waterway, Södertälje lock]
-
A.
Lycksele
Lycksele is a small town in northern Sweden known as a regional service center and gateway to the inland forests and wilderness of Västerbotten.
-
B.
Torsåker
Torsåker is a small locality in central Sweden known for its rural character and historical ties to the surrounding Hofors area.
-
C.
Sköllersta
Sköllersta is a locality in central Sweden situated within Örebro County, known as one of the settlements in Hallsberg Municipality.
-
D.
Söderort
Söderort is the southern suburban part of Stockholm, Sweden, consisting mainly of residential districts located south of the inner-city island of Södermalm.
-
E.
Södertälje Harbour
chosen
Södertälje Harbour is a key port and industrial waterfront area in Södertälje, Sweden, serving as an important hub for maritime transport and logistics.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641286bbc8190886f309de13063bf |
completed | April 20, 2026, 3:07 p.m. |
Created at: April 10, 2026, 1:44 p.m.