Triple
T7685209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 United States House of Representatives elections |
E174097
|
entity |
| Predicate | numberOfMajorParties |
P34865
|
FINISHED |
| Object | 2 |
—
|
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 | Statement: [2008 United States House of Representatives elections, numberOfMajorParties, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfMajorParties Context triple: [2008 United States House of Representatives elections, numberOfMajorParties, 2]
-
A.
hasMajorParties
Indicates that an entity is associated with its primary participating parties or main involved groups.
-
B.
hasNumberOfParties
chosen
Indicates the total count of distinct parties or participants involved in a given relationship, agreement, or event.
-
C.
wasMajorPartyDuring
Indicates that an entity functioned as a major political party during a specified time period or event.
-
D.
mainParties
Indicates the primary entities that are directly and centrally involved in a given relationship, event, or agreement.
-
E.
hasPoliticalParties
Indicates that a political system, country, or region includes one or more organized political parties operating within it.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c706d1f0208190bc5b695aa5736244 |
completed | March 27, 2026, 10:38 p.m. |
| PD | Predicate disambiguation | batch_69c70163dea88190ae729df50e63dfd7 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:02 p.m.