Triple
T14889765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danube Bridge |
E359721
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Ruse |
E70722
|
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: Ruse | Statement: [Danube Bridge, locatedNear, Ruse]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ruse Context triple: [Danube Bridge, locatedNear, Ruse]
-
A.
Ruse
chosen
Ruse is a major Bulgarian city and river port on the Danube, known for its elegant architecture and role as an important economic and transport hub.
-
B.
Ruse
Ruse is a residential suburb in the Macarthur region of Sydney, New South Wales, Australia.
-
C.
Varna
Varna is a major Bulgarian city on the Black Sea coast known as an important economic, cultural, and maritime center.
-
D.
Silistra
Silistra is a historic city in northeastern Bulgaria on the Danube River, known as an important cultural and economic center of the Dobruja region.
-
E.
Shumen
Shumen is a city in northeastern Bulgaria known for its historical significance, including nearby medieval capitals and the Monument to 1300 Years of Bulgaria.
- 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_69d827980cbc8190a0c569ae3940a1d9 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69ded5f6cf5c8190b6b28f58fafe5d59 |
completed | April 15, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffeb7921208190bbf4e1a01c6ec5ee |
completed | May 10, 2026, 2:20 a.m. |
Created at: April 10, 2026, 2:09 a.m.