Triple
T11750426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna Awards |
E279389
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | territorial arbitration decisions |
C29750
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: territorial arbitration decisions Context triple: [Vienna Awards, instanceOf, territorial arbitration decisions]
-
A.
maritime boundary decision
A maritime boundary decision is a formal determination, typically by a court, tribunal, or negotiated agreement, that defines the spatial limits and legal rights of states over adjacent or overlapping maritime zones such as territorial seas, exclusive economic zones, and continental shelves.
-
B.
disputed territory
A disputed territory is a geographic area over which two or more parties claim sovereignty or control, without mutual agreement on its legal or political status.
-
C.
maritime boundary delimitation case
A maritime boundary delimitation case is a legal dispute or proceeding in which states seek the determination or adjustment of their respective maritime zones and boundaries, such as territorial seas, exclusive economic zones, and continental shelves, in accordance with international law.
-
D.
territorial acquisition
Territorial acquisition is the process by which a state or entity gains control over land or geographic space through means such as conquest, cession, purchase, occupation, or accretion.
-
E.
territorial relationship
A territorial relationship is a conceptual association that defines how entities claim, control, share, or interact within a specific geographic or spatial area.
- F. None of above. chosen
Provenance (1 batch)
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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:41 p.m.