Triple

T28354083
Position Surface form Disambiguated ID Type / Status
Subject Eddystone (Remington-UMC) (contract) E718176 entity
Predicate rifleModelProduced P164689 FINISHED
Object P14 Enfield NE NERFINISHED

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: P14 Enfield | Statement: [Eddystone (Remington-UMC) (contract), rifleModelProduced, P14 Enfield]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rifleModelProduced
Context triple: [Eddystone (Remington-UMC) (contract), rifleModelProduced, P14 Enfield]
  • A. modelProduced
    Indicates that a particular model has generated or produced a specified output, result, or artifact.
  • B. tankModelProduced
    Indicates that a particular model or variant of a tank was manufactured or brought into production by some producer or manufacturer.
  • C. Berdan No.1 rifle
    Indicates that an entity is a Berdan No.1 rifle, i.e., it has the identity or classification of that specific rifle model.
  • D. aircraftModelProduced
    Indicates that a specific aircraft model has been manufactured or produced by a particular entity (such as a company or organization).
  • E. isServiceRifleOf
    Indicates that one entity is the designated service rifle used by another entity, typically a military or armed force.
  • 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_69eff6ec27b481908c8d7b86c47893d9 completed April 27, 2026, 11:53 p.m.
NER Named-entity recognition batch_69f64ee0c2788190a94a04ad1902fd5e completed May 2, 2026, 7:22 p.m.
PD Predicate disambiguation batch_69f64caede108190a35cc7cbfead866f completed May 2, 2026, 7:12 p.m.
PDg Predicate description generation batch_69f64e36c57c8190af09470a8d35512b completed May 2, 2026, 7:19 p.m.
Created at: April 28, 2026, 12:48 a.m.