Triple

T29125370
Position Surface form Disambiguated ID Type / Status
Subject Narita International Airport Terminal 3 E738209 entity
Predicate hasPassengerServiceLevel P193599 FINISHED
Object no-frills 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: no-frills | Statement: [Narita International Airport Terminal 3, hasPassengerServiceLevel, no-frills]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPassengerServiceLevel
Context triple: [Narita International Airport Terminal 3, hasPassengerServiceLevel, no-frills]
  • A. hasPassengerServicesType
    Indicates the type or category of passenger services that are provided or associated with an entity.
  • B. hasPassengerServiceBrand
    Indicates that a passenger transport service operates under or is associated with a specific commercial brand or service name.
  • C. hasPassengerServicesTo
    Indicates that a transportation provider operates passenger services connecting one location or entity to another.
  • D. hasPassengerOnlyService
    Indicates that the service provided involves only the transportation of passengers, with no freight or cargo component.
  • E. passengerLevel
    Indicates the relative status, class, or priority assigned to a passenger within a transportation or service context.
  • 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_69f07cb29cdc8190afa55444553de60c completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69fd4d1854988190be093b103a681798 completed May 8, 2026, 2:40 a.m.
PD Predicate disambiguation batch_69fd4c8d1a188190897c24527337814a completed May 8, 2026, 2:38 a.m.
PDg Predicate description generation batch_69fd4d16dd20819096957c40f43cd971 completed May 8, 2026, 2:40 a.m.
Created at: April 28, 2026, 11:28 a.m.