Triple
T14988472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ćuprija |
E373767
|
entity |
| Predicate | historicalRegion |
P915
|
FINISHED |
| Object | Pomoravlje |
E375248
|
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: Pomoravlje | Statement: [Ćuprija, historicalRegion, Pomoravlje]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pomoravlje Context triple: [Ćuprija, historicalRegion, Pomoravlje]
-
A.
Pomoravlje
chosen
Pomoravlje is a central Serbian region known for its fertile plains and settlements along the Morava River basin.
-
B.
Paraćin
Paraćin is a town in central Serbia known as an industrial and transportation hub in the Pomoravlje region.
-
C.
Povljana
Povljana is a coastal municipality and tourist settlement on the island of Pag in Croatia, known for its beaches and Mediterranean landscape.
-
D.
Pojuca
Pojuca is a municipality in the Brazilian state of Bahia that forms part of the greater Salvador metropolitan area.
-
E.
Pomarance
Pomarance is a historic Tuscan town in central Italy, known for its medieval architecture and proximity to the geothermal area of Larderello.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7148a308190a687f4d0d61397c6 |
completed | April 15, 2026, 12:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe8c036bfc8190b01bf2128403f557 |
completed | May 9, 2026, 1:21 a.m. |
Created at: April 10, 2026, 2:53 a.m.