Triple
T5338277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salzburg Airport |
E123878
|
entity |
| Predicate | serves |
P98
|
FINISHED |
| Object | Anif |
E22894
|
NE FINISHED |
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: Anif | Statement: [Salzburg Airport, serves, Anif]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Anif Context triple: [Salzburg Airport, serves, Anif]
-
A.
Anif
chosen
Anif is a small Austrian municipality near Salzburg, known for its historic castle and as a residence of notable figures.
-
B.
Anini
Anini is a remote town in the Dibang Valley district of Arunachal Pradesh in northeastern India, known for its rugged Himalayan terrain and proximity to the Dibang River.
-
C.
Anafi
Anafi is a small, remote Greek island in the Aegean Sea, known for its tranquil beaches, rugged landscapes, and traditional Cycladic architecture.
-
D.
Afif
Afif is a town in central Saudi Arabia known as an inland community within the Riyadh administrative region.
-
E.
Anilio
Anilio is a mountain village in the Metsovo region of Epirus in northwestern Greece, known for its traditional architecture and alpine setting.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85c6ec008190ad7a8a54360387d8 |
completed | March 20, 2026, 5:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf411705ec819083b388d3b8bd5a92 |
completed | March 22, 2026, 1:08 a.m. |
Created at: March 20, 2026, 2 p.m.