Triple
T756389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee on the Budget |
E15565
|
entity |
| Predicate | chair |
P16377
|
FINISHED |
| Object | a federal judge designated by the Chief Justice of the United States |
—
|
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: a federal judge designated by the Chief Justice of the United States | Statement: [Committee on the Budget, chair, a federal judge designated by the Chief Justice of the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chair Context triple: [Committee on the Budget, chair, a federal judge designated by the Chief Justice of the United States]
-
A.
chairType
Indicates the specific kind or category of chair that an entity is classified as.
-
B.
canChair
chosen
Indicates that an entity has the authority or capability to preside over, lead, or chair a meeting, committee, or similar group.
-
C.
otherSeat
Indicates that one entity is the alternative or different seat relative to another seat in a given context.
-
D.
cabinet
Indicates that one entity serves as a cabinet (a storage or enclosure unit) for another entity.
-
E.
hasSeat
Indicates that one entity possesses, provides, or includes a seat for another entity.
- 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_69a493599a0081908da65f3407af1ef2 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a66ab4608190afcd81e6606c5116 |
completed | March 1, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69a4a50348088190873a1446db657a78 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.