Triple
T6309823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Maritsa |
E141470
|
entity |
| Predicate | river |
P165
|
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: [Battle of Maritsa, river, Maritsa River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Maritsa River Context triple: [Battle of Maritsa, river, 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.
Krumovitsa River
The Krumovitsa River is a river in southern Bulgaria that flows through the Eastern Rhodope Mountains before joining the Arda River.
-
D.
Angren River
The Angren River is a waterway in eastern Uzbekistan that flows through the Tashkent Region before joining the Syr Darya.
-
E.
Berland River
The Berland River is a tributary waterway in west-central Alberta, Canada, that flows through forested foothills before joining the Athabasca 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_69c008d00efc8190a36c05b4b4a3bf4b |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0648074b081908ba661651ba705a7 |
completed | March 22, 2026, 9:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c62d2cd75c81908961633a7ccf5dc9 |
completed | March 27, 2026, 7:09 a.m. |
Created at: March 22, 2026, 4:28 p.m.