Triple

T26905465
Position Surface form Disambiguated ID Type / Status
Subject ExpressTram E677238 entity
Predicate isAirside P161319 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: [ExpressTram, isAirside, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isAirside
Context triple: [ExpressTram, isAirside, true]
  • A. hasAirsideCenter
    Indicates that one entity serves as or contains the designated airside center associated with another entity.
  • B. hasAirsideConnection
    Indicates that there is a direct, secure connection between areas past security (airside) of two locations, allowing passengers to transfer without re-clearing security or immigration.
  • C. isLocatedAtAirportType
    Indicates that one entity is situated at, or associated with, an airport of a specified type (e.g., international, regional, military).
  • D. isAirBase
    Indicates that the subject entity functions as a military air base, i.e., a facility used for operating, housing, and supporting aircraft and related activities.
  • E. hasRunwayAccessTo
    Indicates that one location or facility is directly connected to another via a usable runway, allowing aircraft to move between them without leaving runway infrastructure.
  • 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_69eee9bcef1c8190be88586bb902bb9b completed April 27, 2026, 4:44 a.m.
NER Named-entity recognition batch_69f61fb2e9808190a27e6fb40a310d9d completed May 2, 2026, 4 p.m.
PD Predicate disambiguation batch_69f611af72ac819094598dd2530d7411 completed May 2, 2026, 3:01 p.m.
PDg Predicate description generation batch_69f6125e54e0819088ee33a20efcc9e6 completed May 2, 2026, 3:03 p.m.
Created at: April 27, 2026, 5:58 a.m.