Triple
T28229767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shattered |
E711694
|
entity |
| Predicate | hasPoliceProceduralElements |
P192049
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Shattered, hasPoliceProceduralElements, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPoliceProceduralElements Context triple: [Shattered, hasPoliceProceduralElements, true]
-
A.
hasPoliceTheme
Indicates that something features police, law enforcement, or policing activities as a central theme or focus.
-
B.
hasPoliceRole
Indicates that an entity holds or performs a specific role, duty, or function within a police or law enforcement context.
-
C.
policeTools
Indicates that the object is a tool, equipment, or resource used by the police in performing their duties.
-
D.
hasPolicePartner
Indicates that one entity has another entity as its partner in a police or law-enforcement context.
-
E.
policeControl
Indicates that one entity exercises authoritative oversight, regulation, or enforcement power over another, as a police force does over people or areas under its jurisdiction.
- 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_69efb51dfb048190ada79b745c33b363 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: April 27, 2026, 10:51 p.m.