Triple
T7222232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electoral Commission (United States, 1877) |
E150286
|
entity |
| Predicate | electionYearInDispute |
P75688
|
FINISHED |
| Object | 1876 |
—
|
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: 1876 | Statement: [Electoral Commission (United States, 1877), electionYearInDispute, 1876]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electionYearInDispute Context triple: [Electoral Commission (United States, 1877), electionYearInDispute, 1876]
-
A.
reElectionYear
Indicates the year in which an entity is (or is scheduled to be) elected again to the same position or office.
-
B.
wasContestedIn
Indicates that an event, position, or decision was the subject of competition, dispute, or challenge within a particular context or proceeding.
-
C.
notableElectionYear
Indicates that a particular year is recognized as significant or noteworthy in the context of an election involving the given entity.
-
D.
wasContestedBetween
Indicates that an event, position, or resource was the subject of competition or dispute involving two or more opposing parties.
-
E.
hasOfficeContested
Indicates that an individual has been a candidate for a particular public office in an election.
- F. None of above. chosen
Provenance (4 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6e9b42c5c81908c405f161c35ffb4 |
completed | March 27, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6e8b5f6508190af28e06a7959d717 |
completed | March 27, 2026, 8:29 p.m. |
Created at: March 27, 2026, 2:54 p.m.