Triple
T178737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergeant at Arms of the House of Representatives |
E3636
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | law enforcement position |
C312
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: law enforcement position Context triple: [Sergeant at Arms of the House of Representatives, instanceOf, law enforcement position]
-
A.
judicial office
A judicial office is an official position within the judiciary in which an individual is authorized to interpret and apply the law, preside over legal proceedings, and issue binding decisions.
-
B.
executive position
An executive position is a high-level organizational role responsible for setting strategic direction, making major decisions, and overseeing the performance and operations of a company or its key divisions.
-
C.
officer training college
An officer training college is an educational institution that prepares individuals for commissioned leadership roles in the armed forces through academic instruction, military training, and character development.
-
D.
United States federal government position
chosen
A United States federal government position is an official role within the executive, legislative, or judicial branches of the federal government, established by law or regulation to perform specific public duties and functions on behalf of the nation.
-
E.
military officer
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
- F. None of above.
Provenance (1 batch)
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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.