Triple
T22108928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papal conclave of 1830–1831 |
E546362
|
entity |
| Predicate | hadVetoAttempt |
P6515
|
FINISHED |
| Object | Austrian veto against Giacomo Giustiniani |
—
|
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: Austrian veto against Giacomo Giustiniani | Statement: [Papal conclave of 1830–1831, hadVetoAttempt, Austrian veto against Giacomo Giustiniani]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadVetoAttempt Context triple: [Papal conclave of 1830–1831, hadVetoAttempt, Austrian veto against Giacomo Giustiniani]
-
A.
vetoedBy
chosen
Indicates that an action, decision, or proposal was rejected or blocked by a specific entity with veto authority.
-
B.
vetoOverridden
Indicates that a previously issued veto has been nullified or reversed by a sufficient overriding authority or vote.
-
C.
cannotVeto
Indicates that an entity lacks the authority or ability to reject, block, or override a decision, proposal, or action made by another entity.
-
D.
hadVoteIn
Indicates that an entity participated by casting a vote in a particular decision, election, or voting event.
-
E.
vetoType
Indicates the specific kind or category of veto applied in a decision-making or approval 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1291b9c988190b3ddd06d1f40dc78 |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.