Triple
T9618092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 United States House of Representatives elections |
E232268
|
entity |
| Predicate | startOfTermForWinners |
P12287
|
FINISHED |
| Object | 2011-01-03 |
—
|
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: 2011-01-03 | Statement: [2010 United States House of Representatives elections, startOfTermForWinners, 2011-01-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startOfTermForWinners Context triple: [2010 United States House of Representatives elections, startOfTermForWinners, 2011-01-03]
-
A.
termStartOfWinner
chosen
Indicates the starting date or point in time of the winner’s term in a given role or position.
-
B.
firstTermStart
Indicates that an entity marks the starting point or initial term in an ordered sequence, period, or agreement.
-
C.
startDateOfCurrentTermLength
Indicates the calendar date on which the currently active term or period of a defined duration begins.
-
D.
endOfTermOnCourt
Indicates the point in time when an individual's service or tenure on a court officially concludes.
-
E.
nextTermStartDate
Indicates the date on which the next term or period in a sequence is scheduled to begin.
- 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_69ca84867bb88190b4b57dd5a56d5691 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9ab0a15481908945b50c622b71b9 |
completed | April 1, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69ccd5aa1d2c8190a287bf1cf4a3037e |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:09 p.m.