Triple
T21996376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papal conclave, 1730 |
E543215
|
entity |
| Predicate | usedVotingMethod |
P539
|
FINISHED |
| Object | secret ballot |
—
|
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: secret ballot | Statement: [Papal conclave, 1730, usedVotingMethod, secret ballot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedVotingMethod Context triple: [Papal conclave, 1730, usedVotingMethod, secret ballot]
-
A.
votingMethod
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
-
B.
usesVotingBallots
Indicates that one entity conducts or participates in a voting process by employing ballots as the method for casting votes.
-
C.
electionMethod
chosen
Indicates the process or system used to select a candidate or make a decision in an election.
-
D.
usesVotingBody
Indicates that one entity employs or relies on a particular voting body to make decisions or take actions on its behalf.
-
E.
usedVirtualVoting
Indicates that an entity participated in a voting process through virtual or remote means rather than in person.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12765fb0c81908f7b7acda065ee2f |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:19 p.m.