Triple
T20905777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberndorf bei Salzburg |
E514793
|
entity |
| Predicate | bordersWith |
P224
|
FINISHED |
| Object | Laufen |
—
|
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: Laufen | Statement: [Oberndorf bei Salzburg, bordersWith, Laufen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Laufen Context triple: [Oberndorf bei Salzburg, bordersWith, Laufen]
-
A.
Laufen
chosen
Laufen is a historic Bavarian town in southeastern Germany situated on the banks of the Salzach River near the Austrian border.
-
B.
Laufen
Laufen is a small Swiss town in the canton of Basel-Landschaft, known for its historic center and location near the French and German borders.
-
C.
Worblaufen
Worblaufen is a locality in the canton of Bern, Switzerland, known primarily as a residential suburb of Bern and a hub for the Swiss Post’s headquarters.
-
D.
Running
"Running" is a synthpop song by the American band Information Society, known for its danceable electronic sound and club popularity in the 1980s.
-
E.
Running
"Running" is a song featured on the album "Rock Steady" by the American rock band No Doubt.
- 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_69e0b4f8a1108190bce3d31331290ced |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6e9001a8c81909fa1004b5977d04f |
completed | April 21, 2026, 3:03 a.m. |
Created at: April 16, 2026, 12:47 p.m.