Triple
T24792335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Миџор |
E620282
|
entity |
| Predicate | регионУСрбији |
P26347
|
FINISHED |
| Object | источна Србија |
—
|
LITERAL 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: источна Србија | Statement: [Миџор, регионУСрбији, источна Србија]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: регионУСрбији Context triple: [Миџор, регионУСрбији, источна Србија]
-
A.
nearestTownSerbia
Indicates the relationship where a given location is associated with the geographically closest town within the territory of Serbia.
-
B.
countryDuringMontenegrinKingdom
Indicates that a country existed or held that status during the historical period of the Montenegrin Kingdom.
-
C.
countryPortionIn
chosen
Indicates that a specific part or region is located within the boundaries of a particular country.
-
D.
жупанија
Indicates an administrative relationship where an area is designated and governed as a county or district-level jurisdiction.
-
E.
topLevelAdministrativeTerritorialEntity
Indicates that one entity is the primary or highest-level administrative territorial division in which the other entity is located or governed.
- F. None of above.
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_69e2fabe77c8819085f7ce6486248139 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f4110424188190889a13976b16b18a |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:47 a.m.