Triple
T409976
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Senate Education Committee |
E9466
|
entity |
| Predicate | processIncludes |
P13114
|
FINISHED |
| Object | bill 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: bill hearings | Statement: [Senate Education Committee, processIncludes, bill hearings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: processIncludes Context triple: [Senate Education Committee, processIncludes, bill hearings]
-
A.
includes
Indicates that one entity contains, encompasses, or has another entity as a part, member, or subset.
-
B.
programmingIncludes
Indicates that one programming-related entity contains, incorporates, or makes use of another as a part, feature, or component.
-
C.
includesApproach
Indicates that one entity incorporates, utilizes, or is characterized by a particular method, strategy, or approach in relation to another entity or context.
-
D.
includesConstant
Indicates that one entity contains or explicitly references a specific constant value within its definition or structure.
-
E.
partOfProcess
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ed31681c8190ac32334562fb17fd |
completed | Feb. 28, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69a2e9737694819080fde9adcc1aa4d4 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ed3032148190beb3a516e437f8f8 |
completed | Feb. 28, 2026, 1:27 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.