Triple
T30903631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KRG Representation in the European Union |
E787235
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | representation of a sub‑state entity |
C57731
|
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: representation of a sub‑state entity Context triple: [KRG Representation in the European Union, instanceOf, representation of a sub‑state entity]
-
A.
state-like entity
A state-like entity is an abstraction that encapsulates a distinct configuration of conditions or behaviors within a system, often determining how the system responds to inputs at a given time.
-
B.
state-created entity
A state-created entity is an organization or body established by a government under statutory or constitutional authority to perform specific public, administrative, or commercial functions.
-
C.
associated state
An associated state is a political entity that maintains internal self-governance while delegating certain sovereign powers, such as defense or foreign affairs, to a larger, partner state under a formal agreement.
-
D.
associated state
An associated state is a political entity that maintains internal self-government while delegating certain sovereign powers, such as defense or foreign affairs, to a larger, partner state under a formal association agreement.
-
E.
bound state
A bound state is a stable configuration of two or more particles or components held together by a potential or interaction such that they have a total energy lower than the energy required to separate them infinitely.
- 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_69f224bcbcb48190836df847424e4057 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:50 p.m.