Triple

T2861519
Position Surface form Disambiguated ID Type / Status
Subject Second Amendment to the United States Constitution E63332 entity
Predicate heldToProtect P42762 FINISHED
Object individual right to possess firearms 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: individual right to possess firearms | Statement: [Second Amendment to the United States Constitution, heldToProtect, individual right to possess firearms]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heldToProtect
Context triple: [Second Amendment to the United States Constitution, heldToProtect, individual right to possess firearms]
  • A. heldAs
    Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
  • B. held
    Indicates that one entity physically grasped, carried, or kept another entity in its possession or control.
  • C. heldOn
    Indicates that an event or activity takes place at a specific time, date, or occasion.
  • D. heldThat
    Indicates that an entity (often a person or authority) maintained, asserted, or concluded that a particular proposition or judgment is true.
  • E. holding
    Indicates that one entity is physically grasping, carrying, or keeping another entity in its possession or control.
  • 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_69ab4c41e8c08190a9e8f5249cc12610 completed March 6, 2026, 9:50 p.m.
NER Named-entity recognition batch_69abdf8df8288190816767169ea7cbf9 completed March 7, 2026, 8:19 a.m.
PD Predicate disambiguation batch_69abdd123ec48190af50a1859aea50b7 completed March 7, 2026, 8:08 a.m.
PDg Predicate description generation batch_69abddedd72c819094a9c4161af07780 completed March 7, 2026, 8:12 a.m.
Created at: March 6, 2026, 10:02 p.m.