Triple
T9226834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 97th United States Congress |
E221703
|
entity |
| Predicate | totalVotingRepresentatives |
P4273
|
FINISHED |
| Object | 435 |
—
|
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: 435 | Statement: [97th United States Congress, totalVotingRepresentatives, 435]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalVotingRepresentatives Context triple: [97th United States Congress, totalVotingRepresentatives, 435]
-
A.
numberOfRepresentatives
chosen
Indicates the quantity of representatives associated with a given entity or unit.
-
B.
numberOfStatesRepresented
Indicates how many distinct states are represented or covered in a given context or entity.
-
C.
totalNumberOfLegislators
Indicates the total count of legislators associated with a given political body, jurisdiction, or legislative session.
-
D.
differenceFromVotingRepresentatives
Indicates that one entity differs in some specified way from the voting representatives associated with another entity.
-
E.
electRepresentativesTo
Indicates the action by which a group or body chooses individuals to serve as its official representatives in another governing or decision-making body.
- 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_69ca83ec8db08190a9110df8232885d2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccda9ecef48190b8aa0e316d07cec7 |
completed | April 1, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
Created at: March 30, 2026, 7:28 p.m.