Triple

T17771709
Position Surface form Disambiguated ID Type / Status
Subject GAU-12/U E443654 entity
Predicate shellCaseEjection P49676 FINISHED
Object linkless, closed-loop system 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: linkless, closed-loop system | Statement: [GAU-12/U, shellCaseEjection, linkless, closed-loop system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: shellCaseEjection
Context triple: [GAU-12/U, shellCaseEjection, linkless, closed-loop system]
  • A. canEject
    Indicates that one entity has the ability or permission to forcibly remove or expel another entity from a place, system, or context.
  • B. hasEjectionSeat
    Indicates that an object (typically a vehicle or cockpit) is equipped with an ejection seat that allows an occupant to be forcibly expelled for emergency escape.
  • C. hasSlidingMechanism
    Indicates that one entity possesses or incorporates a mechanism that allows parts of it to move smoothly along a track or surface in a sliding motion.
  • D. hasEjecta chosen
    Indicates that one entity produces or is associated with material expelled or thrown out from another entity as a result of an energetic event or process.
  • E. escapementType
    Indicates the specific mechanism or method by which motion or energy is intermittently released or regulated in a system.
  • 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_69d8b9ef17708190bdf7e2adbf14ddc2 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e486005770819085d637279b2334eb completed April 19, 2026, 7:36 a.m.
PD Predicate disambiguation batch_69e3d8d8e538819084f1584426b41d5e completed April 18, 2026, 7:17 p.m.
Created at: April 10, 2026, 10:11 a.m.