Triple
T31389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Capitol Police |
E626
|
entity |
| Predicate | enforces |
P760
|
FINISHED |
| Object | federal law |
—
|
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: federal law | Statement: [United States Capitol Police, enforces, federal law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforces Context triple: [United States Capitol Police, enforces, federal law]
-
A.
prohibits
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
B.
encourages
Indicates actively motivating, supporting, or giving confidence to another entity to pursue an action, behavior, or state.
-
C.
governs
chosen
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
-
D.
establishes
Indicates that one entity initiates, creates, or formally sets up another entity, relationship, or state, often giving it official or recognized status.
-
E.
allows
Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
- 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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
| NER | Named-entity recognition | batch_69a249ec0d288190ac3a0939db61813b |
completed | Feb. 28, 2026, 1:50 a.m. |
| PD | Predicate disambiguation | batch_69a24870417081909c7c01e400c94716 |
completed | Feb. 28, 2026, 1:44 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.