Triple
T944764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Constitution of 1791 |
E20387
|
entity |
| Predicate | royalVetoDuration |
P540
|
FINISHED |
| Object | two consecutive legislatures |
—
|
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: two consecutive legislatures | Statement: [French Constitution of 1791, royalVetoDuration, two consecutive legislatures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: royalVetoDuration Context triple: [French Constitution of 1791, royalVetoDuration, two consecutive legislatures]
-
A.
vetoedBy
Indicates that an action, decision, or proposal was rejected or blocked by a specific entity with veto authority.
-
B.
vetoType
Indicates the specific kind or category of veto applied in a decision-making or approval process.
-
C.
vetoOverrideBy
Indicates that a decision or law previously vetoed by one authority is subsequently overridden and enacted by another authority with sufficient power.
-
D.
termLength
chosen
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
E.
cannotVeto
Indicates that an entity lacks the authority or ability to reject, block, or override a decision, proposal, or action made by another entity.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3a3ed3881908386af140477c514 |
completed | March 1, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69a4b29dc8dc8190b9d33f70f8563d61 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.