Triple

T1755206
Position Surface form Disambiguated ID Type / Status
Subject Aérospatiale E38534 entity
Predicate instanceOf P0 FINISHED
Object defence contractor C5343 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: defence contractor
Context triple: [Aérospatiale, instanceOf, defence contractor]
  • A. defense company chosen
    A defense company is an organization that designs, develops, manufactures, and supports military and security-related products, technologies, and services for governments and authorized entities.
  • B. defence estate
    A defence estate is the collective portfolio of land, buildings, infrastructure, and facilities owned, leased, or managed by a nation's defence organization to support military operations, training, administration, and logistics.
  • C. defense contractor business unit
    A defense contractor business unit is an organizational division within a defense company that focuses on developing, producing, and supporting specific military or security-related products, services, or programs for government and allied customers.
  • D. defense industry business unit
    A defense industry business unit is an organizational division within a defense company that focuses on developing, producing, and supporting specific military or security-related products, services, or technologies for government and allied customers.
  • E. public defender support agency
    A public defender support agency is an organization that provides resources, training, policy advocacy, and administrative or specialized legal support to public defenders to enhance the quality and effectiveness of indigent defense services.
  • F. None of above.

Provenance (1 batch)

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_69a8862bdb2081908aefe831c8aa8017 completed March 4, 2026, 7:21 p.m.
Created at: March 4, 2026, 7:31 p.m.