Triple
T33699277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SI-112 (Municipality of Sevnica) |
E863408
|
entity |
| Predicate | languageOfTerritorialUnitName |
P83216
|
FINISHED |
| Object | Slovene |
—
|
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: Slovene | Statement: [SI-112 (Municipality of Sevnica), languageOfTerritorialUnitName, Slovene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfTerritorialUnitName Context triple: [SI-112 (Municipality of Sevnica), languageOfTerritorialUnitName, Slovene]
-
A.
hasTerritorialUnitOfficialName
Indicates that a territorial unit is associated with its official, legally recognized name.
-
B.
languageOfTopLevelAdministration
Indicates the language officially used by the highest level of an administrative or governmental authority to conduct its functions and affairs.
-
C.
languageOfLocalShortName
Indicates the language in which a local or short-form name for an entity is expressed.
-
D.
hasLanguageOfOfficialName
Indicates that an entity’s official name is expressed in a specified language.
-
E.
primaryUnitNameLanguage
chosen
Indicates the language in which the primary unit name is expressed or defined.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a002e71bdc48190b922f2d3b362d259 |
completed | May 10, 2026, 7:06 a.m. |
| PD | Predicate disambiguation | batch_6a002e1a28708190b65f9e657c770bab |
completed | May 10, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:43 a.m.