Triple
T12825168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheremetyevo Terminal D |
E306630
|
entity |
| Predicate | IATAAirport |
P2569
|
FINISHED |
| Object | SVO |
E42072
|
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: SVO | Statement: [Sheremetyevo Terminal D, IATAAirport, SVO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SVO Context triple: [Sheremetyevo Terminal D, IATAAirport, SVO]
-
A.
SVO
chosen
SVO is the three-letter IATA airport code for Sheremetyevo International Airport, one of Moscow’s major international air hubs in Russia.
-
B.
SVO
SVO is the station code used to identify Square Victoria–OACI, a Montreal Metro station on the Orange Line.
-
C.
SOV
SOV is the National Rail station code for Southend Victoria railway station in Southend-on-Sea, Essex, England.
-
D.
FSVO
FSVO is the Swiss federal authority responsible for overseeing food safety, animal health, and animal welfare in Switzerland.
-
E.
SOU
SOU is the three-letter National Rail station code for Southampton Central railway station in Hampshire, England.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96facb2d48190bc12efc00c9da360 |
completed | April 10, 2026, 9:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68ed4f7388190ba989b8a79bd7c6d |
completed | May 2, 2026, 11:55 p.m. |
Created at: April 9, 2026, 5:32 p.m.