Triple
T26568175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papal conclave of 1758 |
E666746
|
entity |
| Predicate | vetoRightType |
P16002
|
FINISHED |
| Object | jus exclusivae |
—
|
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: jus exclusivae | Statement: [Papal conclave of 1758, vetoRightType, jus exclusivae]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vetoRightType Context triple: [Papal conclave of 1758, vetoRightType, jus exclusivae]
-
A.
vetoType
chosen
Indicates the specific kind or category of veto applied in a decision-making or approval process.
-
B.
vetoedBy
Indicates that an action, decision, or proposal was rejected or blocked by a specific entity with veto authority.
-
C.
vetoScope
Indicates that one party has the authority to reject or block certain decisions, actions, or proposals within a defined domain or set of matters.
-
D.
vetoOverridden
Indicates that a previously issued veto has been nullified or reversed by a sufficient overriding authority or vote.
-
E.
vetoOverrideBy
Indicates that a decision or law previously vetoed by one authority is subsequently overridden and enacted by another authority with sufficient power.
- 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_69ee9cfa21c081909e4e36e087debfc6 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f614a1bc9481908b25759bd74dca2f |
completed | May 2, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 1:56 a.m.