Triple
T29200252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts ratifying convention |
E740248
|
entity |
| Predicate | voteMargin |
P161584
|
FINISHED |
| Object | 19 |
—
|
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: 19 | Statement: [Massachusetts ratifying convention, voteMargin, 19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voteMargin Context triple: [Massachusetts ratifying convention, voteMargin, 19]
-
A.
approvalVoteMargin
Indicates the numerical difference between the number of approval votes received and a comparison threshold or opposing votes in a decision or election.
-
B.
popularVoteMargin
Indicates the difference in the number or percentage of popular votes received by two candidates or options in an election.
-
C.
houseVoteMargin
chosen
Indicates the numerical difference between the number of votes for and against a measure in a legislative house.
-
D.
marginOfVictoryElectoralVotes
Indicates the difference in the number of electoral votes between the winning and losing candidates or parties in an election.
-
E.
marginOf
Indicates the difference or buffer between two related quantities, values, or boundaries, often expressing how much one exceeds or falls short of another.
- 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_69f07cb974108190b7e86ca489a6ebb6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f663c4c37481908462be4bbede5a2b |
completed | May 2, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:06 p.m.