Triple

T34072931
Position Surface form Disambiguated ID Type / Status
Subject International Aero Engines E873822 entity
Predicate instanceOf P0 FINISHED
Object multinational joint venture C56034 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: multinational joint venture
Context triple: [International Aero Engines, instanceOf, multinational joint venture]
  • A. multinational consortium
    A multinational consortium is a collaborative alliance of independent organizations from multiple countries that pool resources, expertise, and risks to pursue shared objectives or large-scale projects.
  • B. multinational organization chosen
    A multinational organization is a large-scale entity that operates, manages, and coordinates business activities across multiple countries through a network of international branches, subsidiaries, or affiliates under a unified strategic framework.
  • C. multinational mission mechanism
    A multinational mission mechanism is a structured framework of processes, agreements, and coordinating bodies that enables multiple countries or organizations to collaboratively plan, resource, and execute a shared mission across borders.
  • D. automotive joint venture
    An automotive joint venture is a strategic business arrangement in which two or more companies collaborate to develop, produce, or distribute vehicles or related technologies while sharing resources, risks, and profits.
  • E. Mongolian–Russian joint venture
    A Mongolian–Russian joint venture is a business entity jointly owned and operated by Mongolian and Russian partners, typically established to collaborate on commercial, industrial, or resource-based projects across the two countries.
  • 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_69f349a566808190a1c63b898f33cddf completed April 30, 2026, 12:23 p.m.
Created at: May 1, 2026, 1:52 a.m.