Triple
T482763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 108th United States Congress |
E9805
|
entity |
| Predicate | legislativeBodySizeSenate |
P4272
|
FINISHED |
| Object | 100 |
—
|
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: 100 | Statement: [108th United States Congress, legislativeBodySizeSenate, 100]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeBodySizeSenate Context triple: [108th United States Congress, legislativeBodySizeSenate, 100]
-
A.
numberOfSenators
chosen
Indicates the total count of senators associated with a given political body, region, or entity.
-
B.
totalNumberOfLegislators
Indicates the total count of legislators associated with a given political body, jurisdiction, or legislative session.
-
C.
numberOfRepresentatives
Indicates the quantity of representatives associated with a given entity or unit.
-
D.
currentRepresentativeChamber
Indicates that an entity currently serves as a representative in a specific legislative chamber.
-
E.
representedInSenate
Indicates that an entity serves as a representative for another entity within a senate or upper legislative chamber.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0b8fe6081909f8ab87bfda6b2d8 |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf321288190b5d560f75782c2cb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.