Triple
T33450178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee of the Whole |
E856614
|
entity |
| Predicate | proceduralStepOf |
P132547
|
FINISHED |
| Object | legislative process |
—
|
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: legislative process | Statement: [Committee of the Whole, proceduralStepOf, legislative process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proceduralStepOf Context triple: [Committee of the Whole, proceduralStepOf, legislative process]
-
A.
stepOfModel
chosen
Indicates that something is a specific step or stage within a larger model or process.
-
B.
stepping
Indicates that an entity is moving its foot or feet to take a step, often as part of walking or changing position.
-
C.
overseesProcedure
Indicates that one entity is responsible for supervising, managing, or directing the execution of a specific procedure performed by another entity.
-
D.
lifecycleStep
Indicates the specific phase or stage an entity is currently in within its overall lifecycle or progression.
-
E.
providesProcedure
Indicates that one entity supplies, makes available, or performs a specific procedure 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:37 a.m.