Triple
T27268319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Södermanland railway line |
E687970
|
entity |
| Predicate | connectsAreaWestOf |
P185625
|
FINISHED |
| Object | Stockholm |
—
|
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: Stockholm | Statement: [Södermanland railway line, connectsAreaWestOf, Stockholm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsAreaWestOf Context triple: [Södermanland railway line, connectsAreaWestOf, Stockholm]
-
A.
connectsArea
Indicates that one area serves as a link or passage between two other areas, enabling movement or interaction between them.
-
B.
connectsAreaNear
Indicates that one entity serves as a link or passage between areas that are geographically close to each other.
-
C.
connectsCentralAreaTo
Indicates a relationship where one element serves as a link or pathway between a central area and another location or component.
-
D.
connectsCentralDistrictsWith
Indicates a relationship where something serves as a link or route joining central districts to one another.
-
E.
connectsToAreaKnownFor
Indicates that something has a direct link or association to a specific area that is recognized or notable for certain characteristics or features.
- 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_69ef3557abc481908bf3c146f0f3356a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f7c33d59808190b647989a093f3488 |
completed | May 3, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c29cf36481908e472d4dcb5573b9 |
completed | May 3, 2026, 9:48 p.m. |
Created at: April 27, 2026, 10:57 a.m.