Triple
T57443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senate Judiciary Committee |
E1135
|
entity |
| Predicate | canConduct |
P1554
|
FINISHED |
| Object | confirmation hearings |
—
|
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: confirmation hearings | Statement: [Senate Judiciary Committee, canConduct, confirmation hearings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canConduct Context triple: [Senate Judiciary Committee, canConduct, confirmation hearings]
-
A.
canRefer
Indicates that one entity has the ability or permission to mention, point to, or direct attention to another entity.
-
B.
conducts
chosen
Indicates that an entity organizes, directs, or carries out an activity, operation, or process involving another entity.
-
C.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
D.
canVoteOn
Indicates that an entity has the right or permission to participate in a decision-making process by casting a vote on a specific item, issue, or proposal.
-
E.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b915c9881908c798f4dacb39f1d |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac6799c8190b508933acc0a4c7d |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.