Triple

T28353997
Position Surface form Disambiguated ID Type / Status
Subject .577 Snider E718173 entity
Predicate designedForConversionSystem P9494 FINISHED
Object Snider conversion of Enfield rifles 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: Snider conversion of Enfield rifles | Statement: [.577 Snider, designedForConversionSystem, Snider conversion of Enfield rifles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: designedForConversionSystem
Context triple: [.577 Snider, designedForConversionSystem, Snider conversion of Enfield rifles]
  • A. isDesignedFor chosen
    Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
  • B. designConvertedTo
    Indicates that one design has been transformed or translated into another design or format.
  • C. isForcedToConvertTo
    Indicates that one entity is compelled, against its will, to change its beliefs, affiliation, or status to match that of another entity.
  • D. hasConversionIssueWith
    Indicates that one entity experiences or is associated with a problem, error, or incompatibility when being converted to or from another entity.
  • E. eraOfConversion
    Indicates the specific historical period or era during which the conversion event or change took place.
  • 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_69eff6ec27b481908c8d7b86c47893d9 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f7be53890081909b1d93f30a8f31c6 completed May 3, 2026, 9:29 p.m.
PD Predicate disambiguation batch_69f7bccacbac8190978976324c67db28 completed May 3, 2026, 9:23 p.m.
Created at: April 28, 2026, 12:48 a.m.