Triple
T23048115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budapest–Székesfehérvár line |
E573933
|
entity |
| Predicate | operator |
P179
|
FINISHED |
| Object | MÁV |
—
|
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: MÁV | Statement: [Budapest–Székesfehérvár line, operator, MÁV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MÁV Context triple: [Budapest–Székesfehérvár line, operator, MÁV]
-
A.
MÁV
chosen
MÁV is the Hungarian State Railways company, responsible for operating most of Hungary’s national rail network and related infrastructure.
-
B.
Austrian Airlines
Austrian Airlines is the flag carrier airline of Austria, operating an extensive network of European and long-haul flights from its main hub in Vienna.
-
C.
Flughafen Wien AG
Flughafen Wien AG is an Austrian publicly listed company that operates and manages Vienna International Airport and related airport services.
-
D.
Tyrolean Airways
Tyrolean Airways was an Austrian regional airline known for operating short-haul routes in the Alps and other European regions.
-
E.
Malev Hungarian Airlines
Malev Hungarian Airlines was the former national flag carrier of Hungary, operating scheduled passenger flights across Europe and beyond until its closure in 2012.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1867a206c81909ff923cbf56f7787 |
completed | April 29, 2026, 4:18 a.m. |
Created at: April 17, 2026, 3:54 p.m.