Triple
T23645634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States House of Representatives |
E584024
|
entity |
| Predicate | committeeStructure |
P12457
|
FINISHED |
| Object | standing committees |
—
|
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: standing committees | Statement: [United States House of Representatives, committeeStructure, standing committees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: committeeStructure Context triple: [United States House of Representatives, committeeStructure, standing committees]
-
A.
committeeSystem
chosen
Indicates that an entity operates under, is governed by, or is organized according to a committee-based decision-making system.
-
B.
groupStructure
Indicates that multiple entities are organized together as a collective unit with some defined internal arrangement or hierarchy.
-
C.
committeeMember
Indicates that an entity serves as a member of a particular committee.
-
D.
workStructure
Indicates how work is organized, arranged, or structured within or between entities.
-
E.
committeeInvolved
Indicates that a committee participates in, contributes to, or is otherwise actively involved in a particular activity, decision, or process.
- 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_69e248fefafc81909656921192f30e80 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b2847ba08190ad2427a82fada698 |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.