Triple

T24555796
Position Surface form Disambiguated ID Type / Status
Subject CFM aftermarket services E607512 entity
Predicate supportsLifecyclePhase P156300 FINISHED
Object entry into service 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: entry into service | Statement: [CFM aftermarket services, supportsLifecyclePhase, entry into service]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsLifecyclePhase
Context triple: [CFM aftermarket services, supportsLifecyclePhase, entry into service]
  • A. coversLifecycleStage
    Indicates that one entity includes, addresses, or spans a particular stage within a defined lifecycle.
  • B. designedForLifecycle
    Indicates that something has been intentionally created or configured to support, align with, or optimize a particular lifecycle or set of lifecycle stages.
  • C. lifecycleType
    Indicates the specific stage or pattern within an entity’s overall lifecycle that characterizes how it begins, evolves, and ends.
  • D. supportsLifecyclePolicies
    Indicates that an entity enables or is compatible with the definition, application, and management of lifecycle policies over time.
  • E. lifecycleBehavior
    Indicates how an entity behaves, changes, or is managed over the course of its existence or lifecycle.
  • F. None of above. chosen

Provenance (4 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_69e2c4cae1b88190825e88d5ce8aa61e completed April 17, 2026, 11:39 p.m.
NER Named-entity recognition batch_69f2a8f1fb9c819086b5bd0b03a853e6 completed April 30, 2026, 12:57 a.m.
PD Predicate disambiguation batch_69f2a6b99e7c8190ba7e2dc8729a314a completed April 30, 2026, 12:47 a.m.
PDg Predicate description generation batch_69f2a846c5bc81909ba50cee483bea91 completed April 30, 2026, 12:54 a.m.
Created at: April 18, 2026, 2:27 a.m.