Triple

T26438384
Position Surface form Disambiguated ID Type / Status
Subject Catalina Airport E665015 entity
Predicate hasLimitedCommercialService P105471 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: [Catalina Airport, hasLimitedCommercialService, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLimitedCommercialService
Context triple: [Catalina Airport, hasLimitedCommercialService, true]
  • A. hasLimitedServiceType
    Indicates that an entity is associated with a service that is restricted in scope, availability, or functionality compared to full or standard service types.
  • B. hasCommercialServices chosen
    Indicates that one entity provides or offers commercial services to another entity or within a specified context.
  • C. hasLimitedCommercialAreas
    Indicates that the subject possesses or is characterized by commercial zones that are restricted in size, extent, or availability.
  • D. hasCommercialFunction
    Indicates that an entity serves a commercial role or purpose, such as engaging in trade, sales, or other profit-oriented activities.
  • E. hasLimitation
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • 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_69ee883c851881909e2ab04efbb3c5fe completed April 26, 2026, 9:48 p.m.
NER Named-entity recognition batch_69f6df450014819099d118e5c2d697fa completed May 3, 2026, 5:38 a.m.
PD Predicate disambiguation batch_69f6de07836481908785cde9c511920b completed May 3, 2026, 5:32 a.m.
Created at: April 26, 2026, 11:55 p.m.