Triple
T19345170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Senate seat from Kansas |
E483856
|
entity |
| Predicate | canVoteOnTreaties |
P135501
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [United States Senate seat from Kansas, canVoteOnTreaties, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canVoteOnTreaties Context triple: [United States Senate seat from Kansas, canVoteOnTreaties, yes]
-
A.
treatyPower
Indicates that one entity holds the authority or capacity to negotiate, conclude, or be bound by treaties with another entity.
-
B.
hasTreatyRight
Indicates that an entity holds a legally recognized right or entitlement established by a formal treaty with another party.
-
C.
hasVetoPower
Indicates that one entity possesses the authority to unilaterally reject or block decisions, actions, or proposals made by another entity or group.
-
D.
treatyRatificationThreshold
Indicates the minimum level of approval or support required for a treaty to be formally ratified or come into legal effect.
-
E.
hasElectoralRight
Indicates that an entity possesses the legal right to participate in elections, typically by voting or standing as a candidate.
- F. None of above. chosen
Provenance (4 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_69d8e8d244f8819080eb1f3491300db2 |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e6185a56b4819089336564959b84df |
completed | April 20, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69e4dd12303c8190a2027c062b2dff40 |
completed | April 19, 2026, 1:48 p.m. |
| PDg | Predicate description generation | batch_69e4df51ac6c819091ce72b07790ffa6 |
completed | April 19, 2026, 1:57 p.m. |
Created at: April 10, 2026, 1:34 p.m.