Triple
T16750174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JAT Yugoslav Airlines |
E407051
|
entity |
| Predicate | notableRoute |
P22
|
FINISHED |
| Object |
Belgrade–Moscow
Belgrade–Moscow is an international air route linking the capitals of Serbia and Russia, historically served as a key connection between the Balkans and Eastern Europe.
|
E1236420
|
NE FINISHED |
How this triple was built (4 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: Belgrade–Moscow | Statement: [JAT Yugoslav Airlines, notableRoute, Belgrade–Moscow]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Belgrade–Moscow Context triple: [JAT Yugoslav Airlines, notableRoute, Belgrade–Moscow]
-
A.
Belgrade–Paris
Belgrade–Paris is an international air route connecting the capital of Serbia with the capital of France.
-
B.
Belgrade–London
Belgrade–London is an international air route connecting the capital of Serbia with the capital of the United Kingdom.
-
C.
Belgrade–New York
Belgrade–New York was a prominent long-haul transatlantic air route connecting the capital of former Yugoslavia with the United States.
-
D.
Moscow–Prague
Moscow–Prague is an international air route connecting the capitals of Russia and the Czech Republic.
-
E.
Belgrade–Frankfurt
Belgrade–Frankfurt is an international air route linking the capital of Serbia with one of Germany’s major financial and transport hubs.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Belgrade–Moscow Triple: [JAT Yugoslav Airlines, notableRoute, Belgrade–Moscow]
Generated description
Belgrade–Moscow is an international air route linking the capitals of Serbia and Russia, historically served as a key connection between the Balkans and Eastern Europe.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Belgrade–Moscow Target entity description: Belgrade–Moscow is an international air route linking the capitals of Serbia and Russia, historically served as a key connection between the Balkans and Eastern Europe.
-
A.
Belgrade–Paris
Belgrade–Paris is an international air route connecting the capital of Serbia with the capital of France.
-
B.
Belgrade–London
Belgrade–London is an international air route connecting the capital of Serbia with the capital of the United Kingdom.
-
C.
Belgrade–New York
Belgrade–New York was a prominent long-haul transatlantic air route connecting the capital of former Yugoslavia with the United States.
-
D.
Moscow–Prague
Moscow–Prague is an international air route connecting the capitals of Russia and the Czech Republic.
-
E.
Belgrade–Frankfurt
Belgrade–Frankfurt is an international air route linking the capital of Serbia with one of Germany’s major financial and transport hubs.
- F. None of above. chosen
Provenance (5 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa265a908190a87fa4612bfe6396 |
completed | April 18, 2026, 3:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb069cf481908e029b26ad96d3b5 |
completed | May 10, 2026, 5:06 p.m. |
| NEDg | Description generation | batch_6a00bc136bfc8190ab93cd8e0e7eaf1c |
completed | May 10, 2026, 5:10 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a00bca0a3808190be3d1d7ebd77cc20 |
completed | May 10, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:21 a.m.