Triple
T11226745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cvetković–Maček Agreement |
E265714
|
entity |
| Predicate | includedRegions |
P97931
|
FINISHED |
| Object | parts of Savska Banovina |
—
|
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: parts of Savska Banovina | Statement: [Cvetković–Maček Agreement, includedRegions, parts of Savska Banovina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedRegions Context triple: [Cvetković–Maček Agreement, includedRegions, parts of Savska Banovina]
-
A.
eligibleRegion
Indicates the geographic area within which something (such as an offer, service, or rule) is valid, applicable, or permitted.
-
B.
exportRegion
Indicates the region or geographic area from which goods, services, or resources are exported.
-
C.
includesUSRegions
Indicates that something contains or covers one or more specified regions within the United States.
-
D.
includedSpecialRegionType
Indicates that a special or designated region is included within another region or context, specifying the type of that included special region.
-
E.
includedTerritoryType
Indicates that one territory type is contained within, or forms part of, another territory type.
- F. None of above. chosen
Provenance (4 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_69d6aac656d48190b275efaa7d6074ee |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8ff7b40819089c835be710bc575 |
completed | April 9, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69d75cfbbb188190861efd5d94fe27da |
completed | April 9, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69d77062271c8190b63da714ab5beff9 |
completed | April 9, 2026, 9:24 a.m. |
Created at: April 8, 2026, 9:30 p.m.