Triple

T26167489
Position Surface form Disambiguated ID Type / Status
Subject RDD E654295 entity
Predicate supportsAirCargo P11980 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: [RDD, supportsAirCargo, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsAirCargo
Context triple: [RDD, supportsAirCargo, yes]
  • A. hasCargoAirline
    Indicates that one entity operates as a cargo airline for, or provides cargo air transport services to, another entity.
  • B. airSupport
    Indicates that one entity provides aerial assistance or backing to another, typically through aircraft-based protection, transport, or attack.
  • C. supportsAircraft
    Indicates that one entity is capable of accommodating, carrying, or enabling the operation of an aircraft.
  • D. supportsCargoType
    Indicates that one entity is capable of handling, transporting, or accommodating a specified type of cargo.
  • E. hasCargoServices chosen
    Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
  • 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_69ee5b44391c81908bdbd8813ba9aa99 completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69fd82ed2a4c81908bd7797fbd2e3d08 completed May 8, 2026, 6:30 a.m.
PD Predicate disambiguation batch_69fd814cc10481908e4f8123d35a5d0c completed May 8, 2026, 6:23 a.m.
Created at: April 26, 2026, 8:33 p.m.