Triple

T26183208
Position Surface form Disambiguated ID Type / Status
Subject M1131 Fire Support Vehicle E654743 entity
Predicate roleInUnit P40371 FINISHED
Object mobile fire support coordination node 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: mobile fire support coordination node | Statement: [M1131 Fire Support Vehicle, roleInUnit, mobile fire support coordination node]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInUnit
Context triple: [M1131 Fire Support Vehicle, roleInUnit, mobile fire support coordination node]
  • A. unitRole chosen
    Indicates the functional role or purpose that a unit serves within a larger system or context.
  • B. roleInCommandStructure
    Indicates that one entity holds a specific position or function within the hierarchical command structure of another entity or organization.
  • C. roleInPersonnelMatters
    Indicates that one entity has a specific function, authority, or involvement in managing or deciding personnel-related matters concerning another entity.
  • D. associatedWithUnitRole
    Indicates that an entity has a connection or linkage to a specific role within a particular unit or organizational subdivision.
  • E. roleInMissions
    Indicates the specific function, duty, or position an entity holds within one or more missions.
  • 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_69ee5b469bc081908fe486453fdad810 completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f7675b12848190a3569cfda29c5b0e completed May 3, 2026, 3:18 p.m.
PD Predicate disambiguation batch_69f762f4b59481909f70074f11825bfb completed May 3, 2026, 3 p.m.
Created at: April 26, 2026, 8:41 p.m.