Triple

T14826188
Position Surface form Disambiguated ID Type / Status
Subject Lambing Flat E348577 entity
Predicate hasLawEnforcementAction P18305 FINISHED
Object arrest of riot leaders 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: arrest of riot leaders | Statement: [Lambing Flat, hasLawEnforcementAction, arrest of riot leaders]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLawEnforcementAction
Context triple: [Lambing Flat, hasLawEnforcementAction, arrest of riot leaders]
  • A. lawEnforcementResponse chosen
    Indicates the actions or measures taken by law enforcement agencies in reaction to an incident, behavior, or situation.
  • B. attemptedArrestBy
    Indicates that one entity tried, but may not have succeeded, to place another entity under arrest.
  • C. lawEnforcementStatus
    Indicates the relationship between an entity and its current standing or condition with respect to law enforcement, such as being under investigation, wanted, detained, or cleared.
  • D. lawEnforcementLabel
    Indicates that an entity has been designated, tagged, or classified by a law enforcement authority for monitoring, identification, or investigative purposes.
  • E. hasReasonForArrest
    Indicates that an arrest is associated with a specific reason or cause.
  • 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_69d822eb8f588190bf53445e730a934f completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69ded0713700819097bbb0352650984b completed April 14, 2026, 11:40 p.m.
PD Predicate disambiguation batch_69de8c13418c819088ff9905ace1416a completed April 14, 2026, 6:48 p.m.
Created at: April 10, 2026, 1:51 a.m.