Triple
T26575218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations list of Non‑Self‑Governing Territories |
E666929
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | political status list |
C6716
|
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: political status list Context triple: [United Nations list of Non‑Self‑Governing Territories, instanceOf, political status list]
-
A.
official state list
chosen
An official state list is an authoritative, government-sanctioned enumeration of entities (such as states, regions, or recognized bodies) that defines their legal or administrative status within a jurisdiction.
-
B.
political entity category
A political entity category is a conceptual classification that groups together types of organized political units—such as states, provinces, municipalities, or international organizations—based on shared structural, legal, or functional characteristics.
-
C.
collection of states
A collection of states is an abstract grouping of distinct conditions or configurations that a system, object, or process can occupy, treated as a unified set for analysis or manipulation.
-
D.
federal government list
A federal government list is an official, organized compilation of entities, items, or information maintained by a national government for regulatory, administrative, or informational purposes.
-
E.
political status hearing
A political status hearing is a formal legal or governmental proceeding in which the political standing, recognition, or governance arrangements of a territory, group, or entity are reviewed, contested, or clarified.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
Created at: April 27, 2026, 2 a.m.