Triple

T10343579
Position Surface form Disambiguated ID Type / Status
Subject Vickers Valiant E243684 entity
Predicate firstVbomberInService P93794 FINISHED
Object true 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: true | Statement: [Vickers Valiant, firstVbomberInService, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: firstVbomberInService
Context triple: [Vickers Valiant, firstVbomberInService, true]
  • A. firstGeneratorCommissioned
    Indicates that the first generator in a system or facility has been officially put into operation or brought online.
  • B. firstDeployedIn
    Indicates the time or place where something (such as a system, product, or technology) was initially put into operational use or service.
  • C. firstDeployedFor
    Indicates that an entity was initially deployed or put into operational use specifically for another entity (such as a project, mission, or organization).
  • D. firstJetAirlinerInServiceFor
    Indicates that the subject is the first jet airliner ever to enter commercial service for the specified operator or context.
  • E. firstDeployed
    Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
  • 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_69d381b22b8c8190aaed476be5f872a9 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e92105888190a08104deb9d0cf1c completed April 7, 2026, 11:23 a.m.
PD Predicate disambiguation batch_69d4df9dc3208190bf1bd106f44f6202 completed April 7, 2026, 10:42 a.m.
PDg Predicate description generation batch_69d4e91ce2008190af252c140370b7f2 completed April 7, 2026, 11:23 a.m.
Created at: April 6, 2026, 11:55 a.m.