Triple
T15105953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European route E40 |
E360786
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | Astrakhan |
E380061
|
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: Astrakhan | Statement: [European route E40, connectsTo, Astrakhan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Astrakhan Context triple: [European route E40, connectsTo, Astrakhan]
-
A.
Astrakhan
chosen
Astrakhan is a historic Russian city near the Caspian Sea, known as a key Volga River port and gateway to the Volga Delta region.
-
B.
Orenburg
Orenburg is a major city in southwestern Russia near the Ural River, historically significant as a frontier fortress and administrative center linking European Russia with Central Asia.
-
C.
Cheboksary
Cheboksary is a major city on the Volga River in western Russia and the capital of the Chuvash Republic.
-
D.
Berdyansk
Berdyansk is a port city in southeastern Ukraine on the northern coast of the Sea of Azov, known for its maritime trade, beaches, and resort facilities.
-
E.
Krasnovodsk
Krasnovodsk, now known as Türkmenbaşy, is a key port city on the eastern shore of the Caspian Sea in western Turkmenistan.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00588f35481909674f161bf0f3918 |
completed | April 15, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fec87ce9808190a862ac5839272711 |
completed | May 9, 2026, 5:39 a.m. |
Created at: April 10, 2026, 3:05 a.m.