Triple
T14774222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skierniewice |
E347212
|
entity |
| Predicate | hasTwinTown |
P919
|
FINISHED |
| Object | Mladenovac |
E152815
|
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: Mladenovac | Statement: [Skierniewice, hasTwinTown, Mladenovac]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mladenovac Context triple: [Skierniewice, hasTwinTown, Mladenovac]
-
A.
Mladenovac
chosen
Mladenovac is a suburban municipality and town located in the southern part of the City of Belgrade, Serbia.
-
B.
Obrenovac
Obrenovac is a suburban municipality of Belgrade in Serbia, known for its industrial facilities and proximity to the Sava River.
-
C.
Baćevac
Baćevac is a village located within the municipality of Barajevo in the Belgrade District of Serbia.
-
D.
Zvornik
Zvornik is a historic town and municipality in northeastern Bosnia and Herzegovina, situated on the banks of the Drina River near the border with Serbia.
-
E.
Jasenica
Jasenica is a river in central Serbia that flows through the Šumadija region before joining the Velika Morava.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec815dd5081909e927911c06b2d66 |
completed | April 14, 2026, 11:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe72a347808190a72dfd3a1b776982 |
completed | May 8, 2026, 11:32 p.m. |
Created at: April 10, 2026, 1:31 a.m.