Triple
T28421683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amendment of the Constitution |
E719955
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of the Debian Constitution |
C23781
|
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: section of the Debian Constitution Context triple: [Amendment of the Constitution, instanceOf, section of the Debian Constitution]
-
A.
Debian Project document
chosen
A Debian Project document is an official or semi-official written artifact produced within the Debian community that records policies, procedures, decisions, or technical information relevant to the development, governance, or use of the Debian operating system.
-
B.
party constitution
A party constitution is a formal document that defines a political party’s fundamental principles, organizational structure, membership rules, and internal decision-making procedures.
-
C.
section of the Belgian Constitution
A section of the Belgian Constitution is a distinct, numbered subdivision that groups together related constitutional provisions governing specific aspects of the Belgian state, its institutions, or fundamental rights.
-
D.
section of political charter
A section of political charter is a distinct, formally delineated subdivision of a foundational governing document that specifies particular principles, rights, structures, or procedures within a political system.
-
E.
constitutional convention
A constitutional convention is a formal gathering of representatives convened to draft, revise, or replace a constitution or fundamental governing framework of a political entity.
- 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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:34 a.m.