Triple

T15613616
Position Surface form Disambiguated ID Type / Status
Subject Police Officer (LAPD rank) E375358 entity
Predicate swornStatus P16364 FINISHED
Object sworn peace officer 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: sworn peace officer | Statement: [Police Officer (LAPD rank), swornStatus, sworn peace officer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: swornStatus
Context triple: [Police Officer (LAPD rank), swornStatus, sworn peace officer]
  • A. hasSwornStatus chosen
    Indicates that an entity is formally bound by an oath or sworn commitment, reflecting an official or pledged status in relation to another entity or role.
  • B. swornInOn
    Indicates that an individual formally assumes an office, role, or duty by taking an official oath on a specified date, occasion, or object.
  • C. oathSwornBefore
    Indicates that an oath or solemn promise has been formally declared in the presence of a specified person, group, or authority.
  • D. mayBeAffirmedRatherThanSworn
    Indicates that a statement or testimony can be confirmed by affirmation instead of being given under a formal oath.
  • E. securedStatus
    Indicates that an entity’s state, access, or data has been protected or locked down to prevent unauthorized use or modification.
  • 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_69d85ccf2794819096cda4cbcb02d478 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04e83407c8190abbcd4b7fab0ff85 completed April 16, 2026, 2:50 a.m.
PD Predicate disambiguation batch_69deda844af081909e658ebc9d9b403d completed April 15, 2026, 12:23 a.m.
Created at: April 10, 2026, 4:13 a.m.