Triple
T9618091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 United States House of Representatives elections |
E232268
|
entity |
| Predicate | termLengthForWinners |
P33746
|
FINISHED |
| Object | 2 years |
—
|
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: 2 years | Statement: [2010 United States House of Representatives elections, termLengthForWinners, 2 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termLengthForWinners Context triple: [2010 United States House of Representatives elections, termLengthForWinners, 2 years]
-
A.
termLength
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
B.
electsTermLength
Indicates the length of time for which an entity is elected to hold a particular position or office.
-
C.
termLengthNumber
chosen
Indicates the numerical value representing the duration or length of a specified term.
-
D.
numberOfTermInOffice
Indicates the specific ordinal count of how many terms an entity has served in a particular office or position.
-
E.
termLengthCondition
Indicates a condition or constraint specifying the required or allowed duration/length of a term (such as a contract, agreement, or period).
- 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.