Triple
T2377796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia congressional delegation |
E46238
|
entity |
| Predicate | totalVotingMembers |
P35990
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Virginia congressional delegation, totalVotingMembers, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: totalVotingMembers Context triple: [Virginia congressional delegation, totalVotingMembers, 13]
-
A.
hasNumberOfVotingMembers
chosen
Indicates the specific count of individuals who hold voting rights within a given group or body.
-
B.
hasVotingMembers
Indicates that certain entities are recognized as having individuals or units with the authority to vote within a group, body, or decision-making process.
-
C.
numberOfFullMembers
Indicates the total count of entities that hold full membership status within a specified group or organization.
-
D.
numberOfAppointedMembers
Indicates the specific count of members who have been formally appointed to a group, body, or position.
-
E.
numberOfElectedMembers
Indicates the total count of individuals who have been formally chosen through an election to serve as members of a given body or group.
- 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_69a88a1554a48190a0180682bcf099be |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.