Triple
T26936814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free Territory of Trieste |
E678407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former independent territory |
C8394
|
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: former independent territory Context triple: [Free Territory of Trieste, instanceOf, former independent territory]
-
A.
former dependent territory
chosen
A former dependent territory is a geographic area that was once politically, economically, or administratively controlled by another sovereign state but has since gained independence or a different political status.
-
B.
non-self-governing territory
A non-self-governing territory is a geographic area under the administrative control of another state where the local population has not yet achieved full self-government or independence.
-
C.
self-governing territory
A self-governing territory is a geographically defined area that exercises autonomous control over its internal affairs under its own local government, while remaining formally subject to a larger sovereign state.
-
D.
United Nations trust territory
A United Nations trust territory is a non-self-governing territory placed under the administration of a member state by the UN Trusteeship Council, with the goal of promoting its advancement toward self-government or independence.
-
E.
former sovereign state
A former sovereign state is a political entity that once possessed full independence and international recognition as a nation but has since lost that status through dissolution, merger, annexation, or other political change.
- F. None of above.
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_69eeeb4cac908190a45956c2993d1cc2 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 6:16 a.m.