Triple
T26329169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New York State University Police |
E662334
|
entity |
| Predicate | hasPolicePowers |
P55637
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [New York State University Police, hasPolicePowers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPolicePowers Context triple: [New York State University Police, hasPolicePowers, yes]
-
A.
lawEnforcementPowers
chosen
Indicates that an entity possesses official authority and legal powers to enforce laws, maintain public order, and carry out related policing actions.
-
B.
hasPoliceRole
Indicates that an entity holds or performs a specific role, duty, or function within a police or law enforcement context.
-
C.
hasPoliceInstitution
Indicates that an entity is associated with, governed by, or served by a particular police institution or law enforcement body.
-
D.
hasOwnPoliceForce
Indicates that an entity maintains and controls its own dedicated police force or law enforcement agency.
-
E.
hasPublicAuthority
Indicates that an entity possesses official power or legal authority to act on behalf of the public or a governing body.
- 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_69ee812f32748190871d970c4e2a8ddf |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
Created at: April 26, 2026, 10:32 p.m.