Triple
T31328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Speaker of the United States House of Representatives |
E624
|
entity |
| Predicate | canBeRemovedBy |
P2359
|
FINISHED |
| Object | majority vote of the House |
—
|
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: majority vote of the House | Statement: [Speaker of the United States House of Representatives, canBeRemovedBy, majority vote of the House]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeRemovedBy Context triple: [Speaker of the United States House of Representatives, canBeRemovedBy, majority vote of the House]
-
A.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
B.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
C.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
-
D.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
E.
isProtectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a249ec0d288190ac3a0939db61813b |
completed | Feb. 28, 2026, 1:50 a.m. |
| PD | Predicate disambiguation | batch_69a24870417081909c7c01e400c94716 |
completed | Feb. 28, 2026, 1:44 a.m. |
| PDg | Predicate description generation | batch_69a249eb52a08190916849b44bd9d68d |
completed | Feb. 28, 2026, 1:50 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.