Triple

T28761540
Position Surface form Disambiguated ID Type / Status
Subject Major Crimes Unit (The Wire) E726126 entity
Predicate operationalPriority P197978 FINISHED
Object wiretap cases over street-level arrests 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: wiretap cases over street-level arrests | Statement: [Major Crimes Unit (The Wire), operationalPriority, wiretap cases over street-level arrests]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operationalPriority
Context triple: [Major Crimes Unit (The Wire), operationalPriority, wiretap cases over street-level arrests]
  • A. managementPriority
    Indicates the relative level of importance or urgency assigned to managing or addressing a particular entity, issue, or task.
  • B. orderPrecedence
    Indicates that one entity must come before another in a defined sequence or priority order.
  • C. programPriority
    Indicates the relative importance or urgency assigned to a program compared to other programs.
  • D. planningPriority
    Indicates the relative importance or urgency assigned to an item, task, or objective when organizing or scheduling plans.
  • E. limitsPriorityOf
    Indicates that one entity imposes a maximum allowable priority level on another entity’s priority.
  • 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_69f03198be14819098fa74e48b3749bf completed April 28, 2026, 4:03 a.m.
NER Named-entity recognition batch_69fec00f27988190955de6b6348a4d97 completed May 9, 2026, 5:03 a.m.
PD Predicate disambiguation batch_69febd52037c8190b475dbd50fdbc13e completed May 9, 2026, 4:51 a.m.
PDg Predicate description generation batch_69fec00e5c1c819083d174bb4bc35f29 completed May 9, 2026, 5:03 a.m.
Created at: April 28, 2026, 6:12 a.m.