Triple
T22612903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 15/33 |
E566759
|
entity |
| Predicate | servesCity |
P82
|
FINISHED |
| Object | Vänersborg |
—
|
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: Vänersborg | Statement: [Runway 15/33, servesCity, Vänersborg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vänersborg Context triple: [Runway 15/33, servesCity, Vänersborg]
-
A.
Vänersborg
chosen
Vänersborg is a Swedish town located at the southern tip of Lake Vänern, known historically as an administrative and trading center.
-
B.
Sandviken
Sandviken is an industrial town in central Sweden, best known as the historic home of the steel company Sandvik.
-
C.
Östervåla
Östervåla is a locality in central Sweden that serves as one of the settlements within Heby Municipality in Uppsala County.
-
D.
Strängnäs
Strängnäs is a historic Swedish town known for its medieval cathedral and picturesque location on the shores of Lake Mälaren.
-
E.
Nykvarn
Nykvarn is a small locality in eastern Sweden that serves as the administrative and population center of Nykvarn Municipality in Stockholm County.
- 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_69e245884860819081046ce07d5872c4 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f167ec03c48190b55394b7296f48e5 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 2:58 p.m.