Triple
T3109647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maritsa |
E64918
|
entity |
| Predicate | majorTributary |
P415
|
FINISHED |
| Object | Tundzha |
E243770
|
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: Tundzha | Statement: [Maritsa, majorTributary, Tundzha]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Tundzha Context triple: [Maritsa, majorTributary, Tundzha]
-
A.
Tundzha River
chosen
The Tundzha River is a significant river in southeastern Europe that flows through Bulgaria and Turkey before joining the Maritsa River.
-
B.
Chardzhev
Chardzhev is the former name of the city now known as Turkmenabat, a major urban center in eastern Turkmenistan.
-
C.
Dessislava
Dessislava was a medieval Bulgarian noblewoman and patron associated with the commissioning and decoration of the Boyana Church near Sofia.
-
D.
Demerdzhi
Demerdzhi is a notable mountain massif in Crimea, famous for its striking rock formations and scenic landscapes.
-
E.
Vidnoye
Vidnoye is a small town in Moscow Oblast, Russia, functioning largely as a residential and industrial satellite of Moscow.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada2a0ab2481908db50738ec3ad0fb |
completed | March 8, 2026, 4:24 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b203902a6881909b20589fad629640 |
completed | March 12, 2026, 12:06 a.m. |
Created at: March 8, 2026, 3:04 p.m.