Triple

T615239
Position Surface form Disambiguated ID Type / Status
Subject Eurofighter GmbH E12188 entity
Predicate keyProgramme P6928 FINISHED
Object NATO-aligned fighter development 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: NATO-aligned fighter development | Statement: [Eurofighter GmbH, keyProgramme, NATO-aligned fighter development]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: keyProgramme
Context triple: [Eurofighter GmbH, keyProgramme, NATO-aligned fighter development]
  • A. hasProgramme chosen
    Indicates that an entity is associated with or offers a particular programme (such as a course of study, plan, or structured set of activities).
  • B. programmeName
    Indicates that an entity has or is identified by a specific programme’s name.
  • C. key
    Indicates that one entity functions as a key (literal or metaphorical) that unlocks, enables access to, or provides a crucial solution or control over another entity.
  • D. keyConference
    Indicates that an entity is a major or primary conference associated with another entity (such as a person, organization, or event).
  • E. programFocus
    Indicates that an educational or training program is primarily oriented around or concentrated on a particular subject, theme, or objective.
  • 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_69a493309df48190a327f748e88049a6 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49e0b438881909ad515adf7a4eb79 completed March 1, 2026, 8:14 p.m.
PD Predicate disambiguation batch_69a49cfbcbf88190a854921dc531eba8 completed March 1, 2026, 8:09 p.m.
Created at: March 1, 2026, 7:35 p.m.