Triple
T6359013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beslan Airport |
E143061
|
entity |
| Predicate | hasCode |
P9567
|
FINISHED |
| Object | URMO |
E587519
|
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: URMO | Statement: [Beslan Airport, hasCode, URMO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: URMO Context triple: [Beslan Airport, hasCode, URMO]
-
A.
URMO
chosen
URMO is the ICAO airport code for Beslan Airport, which serves the city of Vladikavkaz in North Ossetia–Alania, Russia.
-
B.
URU
URU is the FIFA country code used to represent the Uruguay national football team in international competitions and rankings.
-
C.
Urke
Urke is a small village in Norway situated along the scenic Hjørundfjord, known for its dramatic mountain surroundings and fjord landscapes.
-
D.
URM
URM is the National Rail station code for Urmston railway station in Greater Manchester, England.
-
E.
Urambo
Urambo is a town and district headquarters in western Tanzania known historically for tobacco production and its location within the Tabora Region.
- 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_69c008d7a9c4819098d647ec47776917 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c067f72f8481908f9df0c0cdf22a52 |
completed | March 22, 2026, 10:06 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c63869ef148190816b152f2724de49 |
completed | March 27, 2026, 7:57 a.m. |
Created at: March 22, 2026, 4:32 p.m.