Triple
T19680845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ekornavallen |
E472579
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Falkö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: Falköping | Statement: [Ekornavallen, near, Falköping]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Falköping Context triple: [Ekornavallen, near, Falköping]
-
A.
Falköping
chosen
Falköping is a small Swedish town known for its surrounding ancient burial mounds, rolling agricultural landscape, and location between the plateaus of Mösseberg and Ålleberg.
-
B.
Falkenberg
Falkenberg is a coastal town in southwestern Sweden known for its beaches, fishing heritage, and location along the River Ätran.
-
C.
Falkenberg
Falkenberg is a small municipality in the Rottal-Inn district of Lower Bavaria in southeastern Germany.
-
D.
Falkenberg
Falkenberg is a locality in the borough of Lichtenberg in Berlin, Germany, known for its more rural character on the city's northeastern edge.
-
E.
Fagersta
Fagersta is an industrial town in central Sweden known for its steel production and manufacturing heritage.
- 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_69d8e514f2e08190ba70a4449519d218 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641bf97348190bc31b00ed4ec6cad |
completed | April 20, 2026, 3:09 p.m. |
Created at: April 10, 2026, 1:45 p.m.