Triple
T1348604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Protective Operations |
E28828
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Secret Service office |
C6278
|
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: United States Secret Service office Context triple: [Office of Protective Operations, instanceOf, United States Secret Service office]
-
A.
former United States Mint facility
A former United States Mint facility is a decommissioned government building that once produced or processed U.S. coinage and related monetary materials but is no longer in active minting operation.
-
B.
office of the United States Department of State
An office of the United States Department of State is an organizational unit within the Department responsible for carrying out specific foreign policy, diplomatic, administrative, or support functions under its designated mandate.
-
C.
headquarters
The headquarters is the primary location where an organization’s central management, strategic decision-making, and key administrative functions are coordinated and controlled.
-
D.
Inn of Court office
An Inn of Court office is an administrative unit within an Inn of Court responsible for managing membership, education, governance, and day-to-day operations for barristers and student members.
-
E.
division of the United States Capitol Police
A division of the United States Capitol Police is an organizational unit within the agency responsible for specific protective, law enforcement, or administrative functions related to safeguarding the U.S. Capitol complex and its occupants.
- F. None of above. chosen
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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:56 p.m.