Triple

T2970026
Position Surface form Disambiguated ID Type / Status
Subject NATO missions E80256 entity
Predicate typicallyInvolve P23735 FINISHED
Object joint operations of land forces 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: joint operations of land forces | Statement: [NATO missions, typicallyInvolve, joint operations of land forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicallyInvolve
Context triple: [NATO missions, typicallyInvolve, joint operations of land forces]
  • A. involves
    Indicates that an entity participates in, is a part of, or is implicated within a particular event, process, or relationship.
  • B. oftenInvolvedWith chosen
    Indicates that one entity frequently participates in or is commonly associated with activities, events, or situations involving another entity.
  • C. involvesIssue
    Indicates that an action, event, or entity is related to, concerns, or includes a particular issue.
  • D. frontInvolved
    Indicates that an entity is directly involved in or associated with the front (e.g., front line, front-facing part, or leading edge) of another entity or situation.
  • E. typicallySpared
    Indicates that an entity is usually not affected by, excluded from, or left untouched by a particular action, process, or condition.
  • 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_69ad8b14ffe881908ffed62f9595c867 completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69ad997282b481909d078be0e70d9930 completed March 8, 2026, 3:44 p.m.
PD Predicate disambiguation batch_69ad960e71f8819088179d11248c6ed0 completed March 8, 2026, 3:30 p.m.
Created at: March 8, 2026, 2:58 p.m.