Triple

T3866304
Position Surface form Disambiguated ID Type / Status
Subject Rickenbacker International Airport E91861 entity
Predicate hasCargoSpecialization P11980 FINISHED
Object freight distribution 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: freight distribution | Statement: [Rickenbacker International Airport, hasCargoSpecialization, freight distribution]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCargoSpecialization
Context triple: [Rickenbacker International Airport, hasCargoSpecialization, freight distribution]
  • A. hasCargoRole
    Indicates that an entity participates in a cargo-related capacity or function within a transport, shipment, or logistics context.
  • B. hasCargoDivision
    Indicates that an organization possesses a specific division or unit responsible for cargo-related operations or services.
  • C. hasCargoServices chosen
    Indicates that an entity provides or is equipped to handle cargo transportation or freight services for another entity or location.
  • D. hasSpecial
    Indicates that an entity possesses or is associated with a distinctive or exceptional attribute, status, or feature compared to others.
  • E. hasCargoAirline
    Indicates that one entity operates as a cargo airline for, or provides cargo air transport services to, another 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_69aed9645f348190a9868e7cef56ab7e completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aeec3b8d988190b56d42ac1521e19c completed March 9, 2026, 3:50 p.m.
PD Predicate disambiguation batch_69aee754dddc8190936e1f9c40a770db completed March 9, 2026, 3:29 p.m.
Created at: March 9, 2026, 3:19 p.m.