Triple
T25795080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitution of 16 April 1871 |
E649657
|
entity |
| Predicate | definedLegislatureType |
P15791
|
FINISHED |
| Object | bicameral legislature |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: bicameral legislature | Statement: [Constitution of 16 April 1871, definedLegislatureType, bicameral legislature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definedLegislatureType Context triple: [Constitution of 16 April 1871, definedLegislatureType, bicameral legislature]
-
A.
hasLegislatureType
chosen
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
B.
hasLegislativeType
Indicates that something is associated with, classified by, or characterized as a particular type or category of legislation or legislative measure.
-
C.
typeOfLegislation
Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
-
D.
advocatedLegislatureType
Indicates that an entity publicly supported or promoted a particular type or form of legislature.
-
E.
legislativeBase
Indicates that one entity serves as the legal or legislative basis, authority, or foundation for another entity or action.
- F. None of above.
Provenance (3 batches)
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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 22, 2026, 6:28 a.m.