Triple
T10334267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pinckney Plan |
E242958
|
entity |
| Predicate | proposedVetoPower |
P72417
|
FINISHED |
| Object | executive and judiciary joint veto |
—
|
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: executive and judiciary joint veto | Statement: [Pinckney Plan, proposedVetoPower, executive and judiciary joint veto]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposedVetoPower Context triple: [Pinckney Plan, proposedVetoPower, executive and judiciary joint veto]
-
A.
vetoedBy
Indicates that an action, decision, or proposal was rejected or blocked by a specific entity with veto authority.
-
B.
hasVetoPower
chosen
Indicates that one entity possesses the authority to unilaterally reject or block decisions, actions, or proposals made by another entity or group.
-
C.
vetoType
Indicates the specific kind or category of veto applied in a decision-making or approval process.
-
D.
vetoOverrideBy
Indicates that a decision or law previously vetoed by one authority is subsequently overridden and enacted by another authority with sufficient power.
-
E.
voteFor
Indicates that one entity casts or expresses a vote in favor of another entity or option.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:53 a.m.