Triple
T7477520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1954 United States Capitol shooting |
E176666
|
entity |
| Predicate | chamberTargeted |
P76479
|
FINISHED |
| Object | House chamber |
—
|
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: House chamber | Statement: [1954 United States Capitol shooting, chamberTargeted, House chamber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chamberTargeted Context triple: [1954 United States Capitol shooting, chamberTargeted, House chamber]
-
A.
chamberedFor
Indicates that a firearm is designed or configured to safely accept and fire a specific cartridge or ammunition type in its chamber.
-
B.
chamber1
Indicates that an entity is a chamber or room, typically serving as an enclosed space within a larger structure.
-
C.
chamber2
Indicates that one entity serves as a secondary or inner chamber, room, or compartment associated with another entity.
-
D.
forChamber
Indicates that something is intended for use in, associated with, or belonging to a particular chamber.
-
E.
chamberOf
Indicates that one entity is a chamber, room, or enclosed space that is part of, contained within, or assigned to another entity.
- 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_69c69f236ce08190a04d7679f03b29b2 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f4f0088c8190880770ac31e5b7a7 |
completed | March 27, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69c6f03d967081908a8e696ff9693b90 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f105e320819091db3cdb1f1351f0 |
completed | March 27, 2026, 9:05 p.m. |
Created at: March 27, 2026, 3:41 p.m.