Triple
T18693642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Part VI of the Basic Law |
E457060
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | section of a constitutional document |
C9595
|
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 a constitutional document Context triple: [Part VI of the Basic Law, instanceOf, section of a constitutional document]
-
A.
part of a constitutional statute
chosen
A part of a constitutional statute is a distinct, formally designated subdivision of the statute that organizes and groups related constitutional provisions under a common thematic or functional heading.
-
B.
section of a legal document
A section of a legal document is a distinct, numbered subdivision that organizes related provisions, rights, and obligations under a specific heading within the overall legal text.
-
C.
legislative document section
A legislative document section is a distinct, numbered subdivision of a law or bill that organizes and specifies particular rules, provisions, or definitions within the overall legislative text.
-
D.
constitutional provision
A constitutional provision is a specific, authoritative rule or principle written into a constitution that defines the structure, powers, and limits of government and the rights of individuals.
-
E.
clause of the United States Constitution
A clause of the United States Constitution is a distinct, self-contained provision within the document that establishes specific powers, rights, limitations, or procedures governing the federal government and its relationship to the states and the people.
- 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.