Triple
T15884935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morava river system |
E385167
|
entity |
| Predicate | majorRiver |
P165
|
FINISHED |
| Object | Jablanica |
E1216009
|
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: Jablanica | Statement: [Morava river system, majorRiver, Jablanica]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jablanica Context triple: [Morava river system, majorRiver, Jablanica]
-
A.
Jablanica
chosen
Jablanica is a river in southern Serbia that serves as one of the principal tributaries feeding the South Morava.
-
B.
Jablanica
Jablanica is a town in Bosnia and Herzegovina known for its location in the Neretva River valley and its historical World War II railway bridge.
-
C.
Jablanica
Jablanica is a river in western Serbia that serves as one of the headwaters forming the Kolubara River.
-
D.
Majdanpek
Majdanpek is a Serbian mining town known for its large copper deposits and surrounding mountainous, forested landscapes in eastern Serbia.
-
E.
Mladenovac
Mladenovac is a suburban municipality and town located in the southern part of the City of Belgrade, Serbia.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1561997bc8190a40e7d68defbbddd |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a007d9849a08190a575f19e816e6df2 |
completed | May 10, 2026, 12:44 p.m. |
Created at: April 10, 2026, 4:51 a.m.