Triple
T18796754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Motala |
E459653
|
entity |
| Predicate | locatedNorthOf |
P305
|
FINISHED |
| Object | Linköping |
—
|
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: Linköping | Statement: [Motala, locatedNorthOf, Linköping]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Linköping Context triple: [Motala, locatedNorthOf, Linköping]
-
A.
Linköping
chosen
Linköping is a major city in southern Sweden known for its university, high-tech industry, and historic cathedral.
-
B.
Lidköping
Lidköping is a Swedish town on the southern shore of Lake Vänern known for its historic center, ceramics industry, and role as a local commercial hub.
-
C.
Nyköping
Nyköping is a historic coastal town in southeastern Sweden known for its medieval castle, harbor, and role as a regional administrative and cultural center.
-
D.
Norrköping
Norrköping is a historic industrial city in eastern Sweden known for its preserved textile mills, waterways, and cultural institutions.
-
E.
Jönköping
Jönköping is a city in southern Sweden, located at the southern end of Lake Vättern and known as a regional commercial and logistical hub.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a01ed3c08190890d9518ed69fdee |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 10, 2026, 11:53 a.m.