Triple

T6486755
Position Surface form Disambiguated ID Type / Status
Subject Canadair Challenger E146530 entity
Predicate canBeConfiguredFor P66130 FINISHED
Object up to around 19 passengers 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: up to around 19 passengers | Statement: [Canadair Challenger, canBeConfiguredFor, up to around 19 passengers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: canBeConfiguredFor
Context triple: [Canadair Challenger, canBeConfiguredFor, up to around 19 passengers]
  • A. canBeAdaptedBy
    Indicates that one entity is capable of being modified, adjusted, or tailored for use by another entity.
  • B. canBeActivatedFor
    Indicates that one entity is capable of being put into an active or operational state by or for another entity.
  • C. canBe
    Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
  • D. configurationAvailable chosen
    Indicates that a specific configuration option or setup is present and can be used or applied in the given context.
  • E. canBeEstablishedBy
    Indicates that a particular state, condition, or relationship is able to be brought into existence or made valid through the actions or intervention of a specified entity.
  • 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_69c0090158c08190af0df9a2348d2d52 completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c06a706d4c8190b7a3cc8855abcecb completed March 22, 2026, 10:17 p.m.
PD Predicate disambiguation batch_69c0673f6d48819080e10c85155c7195 completed March 22, 2026, 10:03 p.m.
Created at: March 22, 2026, 4:52 p.m.