Triple

T7410227
Position Surface form Disambiguated ID Type / Status
Subject Marine Corps Artillery Detachment E170981 entity
Predicate hasTrainingMission P3116 FINISHED
Object train Marine Corps artillery personnel 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: train Marine Corps artillery personnel | Statement: [Marine Corps Artillery Detachment, hasTrainingMission, train Marine Corps artillery personnel]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTrainingMission
Context triple: [Marine Corps Artillery Detachment, hasTrainingMission, train Marine Corps artillery personnel]
  • A. hasTrainingFor
    Indicates that an entity has received or possesses training that prepares it for performing a specific task, role, or function.
  • B. hasTrainingRole
    Indicates that an entity holds or is assigned a specific role within a training or instructional context.
  • C. hasMissionActivity chosen
    Indicates that an entity is associated with, performs, or is involved in a specific mission-related activity.
  • D. isTargetOfMission
    Indicates that an entity is the intended objective or focus of a particular mission or operation.
  • E. hasMissionSystem
    Indicates that an entity is equipped with or associated with a specific mission-related system or subsystem.
  • 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_69c68a618bdc81908d8018edadecd1a4 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f29d77848190a6170eb25483224f completed March 27, 2026, 9:11 p.m.
PD Predicate disambiguation batch_69c6f0323b2c819098ab72c33e6d8534 completed March 27, 2026, 9:01 p.m.
Created at: March 27, 2026, 3:11 p.m.