Triple

T26065011
Position Surface form Disambiguated ID Type / Status
Subject M1134 Anti-Tank Guided Missile Vehicle E657374 entity
Predicate hasMissileLauncherConfiguration P81404 FINISHED
Object twin-rail launcher 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: twin-rail launcher | Statement: [M1134 Anti-Tank Guided Missile Vehicle, hasMissileLauncherConfiguration, twin-rail launcher]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMissileLauncherConfiguration
Context triple: [M1134 Anti-Tank Guided Missile Vehicle, hasMissileLauncherConfiguration, twin-rail launcher]
  • A. missileLauncherConfiguration chosen
    Indicates the specific setup or arrangement of components and parameters that define how a missile launcher is equipped and operates.
  • B. usesMissileSystem
    Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
  • C. missileLaunchCapability
    Indicates that an entity has the ability or functionality to launch missiles.
  • D. numberOfMissilesPerLauncher
    Indicates the quantity of missiles assigned to or carried by each individual launcher.
  • E. hasMissileDetectionSystem
    Indicates that an entity is equipped with a system capable of detecting missiles.
  • 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_69ee5bbd788481909e22bd7153d0c037 completed April 26, 2026, 6:38 p.m.
NER Named-entity recognition batch_69f650c70d7c819093d9a0f005f7c8d5 completed May 2, 2026, 7:30 p.m.
PD Predicate disambiguation batch_69f64cab1f648190a2a9460690d18a37 completed May 2, 2026, 7:12 p.m.
Created at: April 26, 2026, 7:22 p.m.