Triple
T22291151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federation of Malaya Agreement 1948 |
E550998
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | constitutional agreement |
C25343
|
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: constitutional agreement Context triple: [Federation of Malaya Agreement 1948, instanceOf, constitutional agreement]
-
A.
constitutional accord
chosen
A constitutional accord is a formal agreement among key political actors or jurisdictions that defines, revises, or clarifies the fundamental rules, powers, and structures of a constitutional system.
-
B.
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.
-
C.
constitutional convention document
A constitutional convention document is the formal written record produced by a constitutional convention that outlines proposed or adopted foundational principles, governmental structures, and legal frameworks for a political entity.
-
D.
constitutional instrument
A constitutional instrument is a formal legal document or set of provisions that establishes, organizes, or amends the fundamental principles and structures of a state or governing entity.
-
E.
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.
- 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_69e11e45fb848190a1b2ae21296e3a5f |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:41 p.m.