Triple
T8305343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contract with America |
E194449
|
entity |
| Predicate | numberOfProposals |
P48278
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Contract with America, numberOfProposals, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfProposals Context triple: [Contract with America, numberOfProposals, 10]
-
A.
numberOfPropositions
chosen
Indicates the total count of distinct propositions associated with or contained within a given entity or context.
-
B.
numberOfBallots
Indicates the total count of ballots associated with a particular election, contest, or voting event.
-
C.
proposes
Indicates that one entity formally suggests or puts forward an idea, plan, or course of action to another entity for consideration or approval.
-
D.
relatedProposal
Indicates that one proposal has a specified relationship or association with another proposal.
-
E.
notableProposal
Indicates that an entity is a proposal distinguished by particular significance, impact, or recognition compared to other proposals.
- 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_69ca82e613e88190bf8139669bbd0d53 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7e8db3a8819083772db5c7a2454b |
completed | March 31, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69cb70bb3a708190bc705222092da614 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 5:54 p.m.