Triple

T34072964
Position Surface form Disambiguated ID Type / Status
Subject International Aero Engines E873822 entity
Predicate hasJointVentureStructure P26627 FINISHED
Object yes 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: yes | Statement: [International Aero Engines, hasJointVentureStructure, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasJointVentureStructure
Context triple: [International Aero Engines, hasJointVentureStructure, yes]
  • A. hasJointVenture chosen
    Indicates that two or more entities are engaged together in a formally established joint business venture or collaborative commercial undertaking.
  • B. hasJointVenturePartner
    Indicates that an entity is engaged in a joint venture relationship with another entity as a formal business partner.
  • C. formerJointVentureWith
    Indicates that two entities were previously engaged together in a joint venture relationship that has since ended.
  • D. subsidiaryOrJointVenture
    Indicates that one organization is either a subsidiary of, or a jointly owned venture with, another organization.
  • E. requiresForJointVentures
    Indicates that one entity sets conditions or prerequisites that must be met by another entity in order to establish or participate in joint ventures.
  • 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_69f349a566808190a1c63b898f33cddf completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f70bd02e0c8190a1b88d3ff6e64ad2 completed May 3, 2026, 8:48 a.m.
PD Predicate disambiguation batch_69f70ac0170c819098e3b8e41d02efef completed May 3, 2026, 8:43 a.m.
Created at: May 1, 2026, 1:52 a.m.