Triple
T131257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 86th United States Congress |
E2657
|
entity |
| Predicate | numberOfVotingRepresentatives |
P4273
|
FINISHED |
| Object | 437 |
—
|
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: 437 | Statement: [86th United States Congress, numberOfVotingRepresentatives, 437]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfVotingRepresentatives Context triple: [86th United States Congress, numberOfVotingRepresentatives, 437]
-
A.
numberOfRepresentatives
chosen
Indicates the quantity of representatives associated with a given entity or unit.
-
B.
numberOfColoniesRepresented
Indicates the count of distinct colonies that are represented or involved in relation to a given entity or context.
-
C.
numberOfSenators
Indicates the total count of senators associated with a given political body, region, or entity.
-
D.
hasElectoralVotes
Indicates that a political entity (such as a state or district) possesses a specified number of votes in an electoral system used to choose an officeholder.
-
E.
electoralVotesNeededToWin
Indicates the minimum number of electoral votes a candidate must obtain in an election to be declared the winner.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a25855baf48190a1b63f2e5865d957 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a2564edb488190974dc00eb9ac37d9 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.