Triple
T33637356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States presidential election of 1820 |
E861732
|
entity |
| Predicate | wasEffectivelyUncontested |
P29084
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [United States presidential election of 1820, wasEffectivelyUncontested, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasEffectivelyUncontested Context triple: [United States presidential election of 1820, wasEffectivelyUncontested, true]
-
A.
isUncontested
Indicates that something is not challenged, opposed, or disputed by any other party.
-
B.
unsuccessfullyContested
Indicates that an attempt was made to challenge or dispute something, but the challenge did not succeed.
-
C.
resultContested
Indicates that the outcome or result of an event, process, or decision is being challenged or disputed by one or more parties.
-
D.
wasContestedIn
Indicates that an event, position, or decision was the subject of competition, dispute, or challenge within a particular context or proceeding.
-
E.
unopposedOrMinimalOpposition
chosen
Indicates that an action, decision, or process occurs with no opposition or only negligible resistance or objection.
- 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.