Triple
T31120354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oklahoma congressional delegation |
E793204
|
entity |
| Predicate | hasSenatorialClass |
P35716
|
FINISHED |
| Object | Class 2 |
—
|
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: Class 2 | Statement: [Oklahoma congressional delegation, hasSenatorialClass, Class 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSenatorialClass Context triple: [Oklahoma congressional delegation, hasSenatorialClass, Class 2]
-
A.
isPartOfSenateClassSystem
chosen
Indicates that an entity belongs to or is categorized within a specific class or grouping of the Senate class system.
-
B.
hasSenateSeatsSince
Indicates that an entity has held a specified number of seats in a senate starting from a particular point in time.
-
C.
hasVotingRightInSenate
Indicates that an entity possesses the legal right to participate in voting within a senate body.
-
D.
hasUSSenator
Indicates that a specified state or jurisdiction is represented by a particular individual serving as a United States Senator.
-
E.
senateMembership
Indicates that an entity holds or has held a position as a member of a senate.
- 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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fedec693b08190b0f8bfdb921e0766 |
completed | May 9, 2026, 7:14 a.m. |
| PD | Predicate disambiguation | batch_69fede16c1d48190a20d8a9c5722c307 |
completed | May 9, 2026, 7:11 a.m. |
Created at: April 29, 2026, 9:04 p.m.