Triple
T5340951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senate Committee on Banking, Housing, and Urban Affairs |
E123941
|
entity |
| Predicate | hasLegislativeType |
P63102
|
FINISHED |
| Object | oversight |
—
|
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: oversight | Statement: [Senate Committee on Banking, Housing, and Urban Affairs, hasLegislativeType, oversight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegislativeType Context triple: [Senate Committee on Banking, Housing, and Urban Affairs, hasLegislativeType, oversight]
-
A.
hasLegislatureType
Indicates the specific form or system of legislature that an entity possesses or operates under.
-
B.
advocatedLegislatureType
Indicates that an entity publicly supported or promoted a particular type or form of legislature.
-
C.
typeOfLegislation
Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
-
D.
hasLegislativePower
Indicates that an entity possesses the authority to create, amend, or repeal laws within a given jurisdiction or governing framework.
-
E.
hasLegislativeSubject
Indicates that a legislative document, action, or body concerns, addresses, or is about a particular subject or topic.
- 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85e86edc81908d87933db6489f91 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845a62b081909782863865b257a9 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd85e69e808190b29548670fd2900a |
completed | March 20, 2026, 5:37 p.m. |
Created at: March 20, 2026, 2 p.m.