Triple
T5233307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DPD |
E118158
|
entity |
| Predicate | canSubmitBillsOn |
P16006
|
FINISHED |
| Object | regional autonomy |
—
|
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: regional autonomy | Statement: [DPD, canSubmitBillsOn, regional autonomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSubmitBillsOn Context triple: [DPD, canSubmitBillsOn, regional autonomy]
-
A.
canRejectBills
Indicates the authority or power an entity has to refuse approval of proposed bills or legislative measures.
-
B.
canAmendBills
Indicates that an entity has the authority or ability to modify, revise, or propose changes to bills.
-
C.
passesBillsBy
Indicates that one entity successfully approves or enacts bills or legislation through the actions or decisions of another entity.
-
D.
canInitiateLegislation
chosen
Indicates that the subject has the authority or power to formally propose or introduce new legislation or legal measures.
-
E.
canElect
Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
- 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_69bd4466fb8c819083b806a79414d7e4 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b0389048190b55b7c44fe657044 |
completed | March 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69bd77bf1ef08190bb3487b3f3ee088c |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:49 p.m.