Triple
T12393447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow–Prague |
E296054
|
entity |
| Predicate | hasName |
P744
|
FINISHED |
| Object | Moscow–Prague |
E296054
|
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: Moscow–Prague | Statement: [Moscow–Prague, hasName, Moscow–Prague]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Moscow–Prague Context triple: [Moscow–Prague, hasName, Moscow–Prague]
-
A.
Moscow–Prague
chosen
Moscow–Prague is an international air route connecting the capitals of Russia and the Czech Republic.
-
B.
Paris–Prague
Paris–Prague was an international air route connecting the French and Czech capitals, served by the early 20th-century French airline Air Union.
-
C.
Prague–Plzeň
Prague–Plzeň is a major transport corridor in the Czech Republic connecting the capital city of Prague with the industrial city of Plzeň and serving as an important route for regional and international traffic.
-
D.
Prague-Libeň
Prague-Libeň is a district of Prague, Czech Republic, historically notable as the site of the World War II Operation Anthropoid assassination of Reinhard Heydrich.
-
E.
Prazhskaya
Prazhskaya is a Moscow Metro station named after Prague, featuring Soviet-era architecture with Czech design influences.
- 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_69d6ad9e653c8190b1473c860ee53dae |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d93fd228488190b216abd1c341563c |
completed | April 10, 2026, 6:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6347c239881909a031e9e195080c9 |
completed | May 2, 2026, 5:29 p.m. |
Created at: April 8, 2026, 9:54 p.m.