Triple
T28861433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connecticut congressional delegation |
E728873
|
entity |
| Predicate | politicalPartyMajority |
P34082
|
FINISHED |
| Object | Democratic Party |
—
|
NE NERFINISHED |
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: Democratic Party | Statement: [Connecticut congressional delegation, politicalPartyMajority, Democratic Party]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalPartyMajority Context triple: [Connecticut congressional delegation, politicalPartyMajority, Democratic Party]
-
A.
majorityPartyInHouse
chosen
Indicates that a given political party holds more seats than any other party in a specified legislative house.
-
B.
governmentMajorityStatus
Indicates whether a government holds a majority, minority, or other status in the relevant legislative or governing body.
-
C.
senateMajorityLeaderParty
Indicates which political party the Senate Majority Leader belongs to.
-
D.
politicalPartyUsuallyHolding
Indicates the political party that typically holds or controls a given office, position, or jurisdiction.
-
E.
majorParty1
Indicates that the subject entity is the primary or first major party involved in a relationship, agreement, or event.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: April 28, 2026, 6:47 a.m.