Triple

T23062340
Position Surface form Disambiguated ID Type / Status
Subject Joint Surveillance Target Attack Radar System program E574937 entity
Predicate supportedRole P10797 FINISHED
Object battle management 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: battle management | Statement: [Joint Surveillance Target Attack Radar System program, supportedRole, battle management]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportedRole
Context triple: [Joint Surveillance Target Attack Radar System program, supportedRole, battle management]
  • A. supportsRole chosen
    Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
  • B. supportedActor
    Indicates that one entity provided assistance, resources, or endorsement to another entity (the supported actor).
  • C. providedRole
    Indicates that one entity has assigned or supplied a specific role or function to another entity.
  • D. supportedAct
    Indicates that one entity provided assistance, endorsement, or backing for a particular action or activity performed by another entity.
  • E. supportedRight
    Indicates that one entity endorsed, upheld, or actively backed the right or entitlement held by another entity.
  • 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_69e245bd6e4c8190bb8942245b68cad5 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f189a0c3c881909f137ad511c216ac completed April 29, 2026, 4:31 a.m.
PD Predicate disambiguation batch_69ef89d5f71881908b9f9d0c8aab278c completed April 27, 2026, 4:07 p.m.
Created at: April 17, 2026, 3:55 p.m.