Triple
T5050664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippopolis |
E113775
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Maritsa River |
E64918
|
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: Maritsa River | Statement: [Philippopolis, locatedOn, Maritsa River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maritsa River Context triple: [Philippopolis, locatedOn, Maritsa River]
-
A.
Maritsa
chosen
Maritsa is a significant river in the Balkans that flows through Bulgaria, Greece, and Turkey before emptying into the Aegean Sea.
-
B.
Iskar River
The Iskar River is a significant river in Bulgaria that flows south through Sofia before turning north to cut a dramatic gorge through the Balkan Mountains on its way to the Danube.
-
C.
Angren River
The Angren River is a waterway in eastern Uzbekistan that flows through the Tashkent Region before joining the Syr Darya.
-
D.
Selemdzha River
The Selemdzha River is a significant river in Russia’s Amur Oblast, known for its remote taiga landscapes and role in the regional hydrological system.
-
E.
Tundzha River
The Tundzha River is a significant river in southeastern Europe that flows through Bulgaria and Turkey before joining the Maritsa River.
- 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_69bd44391fc48190a311ce9c826c209b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7425df74819091cfde348dd16a68 |
completed | March 20, 2026, 4:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bec35a3314819091a1520d3a366869 |
completed | March 21, 2026, 4:12 p.m. |
Created at: March 20, 2026, 1:37 p.m.