Triple

T15239786
Position Surface form Disambiguated ID Type / Status
Subject MBDA Germany E364224 entity
Predicate parentOrganization P254 FINISHED
Object MBDA E1101078 NE 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: MBDA | Statement: [MBDA Germany, parentOrganization, MBDA]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: MBDA
Context triple: [MBDA Germany, parentOrganization, MBDA]
  • A. MBDA
    MBDA is a U.S. federal agency dedicated to promoting the growth and competitiveness of minority-owned businesses through programs, services, and advocacy.
  • B. MBDA chosen
    MBDA is a leading European multinational developer and manufacturer of missile systems and related defense technologies.
  • C. MBDA France
    MBDA France is a major European defense company specializing in the design and production of advanced missile systems and related technologies.
  • D. MBDA Italy
    MBDA Italy is the Italian branch of the European missile systems company MBDA, specializing in the design and production of advanced missile and air-defense technologies.
  • E. MBDA Germany
    MBDA Germany is a defense company specializing in the development and production of advanced missile systems and guided weapons for military applications.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d85a0dde7481908fc64d1e82d5d20d completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e007db9a148190aadea8d5f8b6b261 completed April 15, 2026, 9:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69fedd41b7c48190917385c6c61370b2 completed May 9, 2026, 7:07 a.m.
Created at: April 10, 2026, 3:12 a.m.