Triple

T2776387
Position Surface form Disambiguated ID Type / Status
Subject Gibraltar Airport E61579 entity
Predicate hasSafetyMeasure P34538 FINISHED
Object road barriers for runway crossings 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: road barriers for runway crossings | Statement: [Gibraltar Airport, hasSafetyMeasure, road barriers for runway crossings]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSafetyMeasure
Context triple: [Gibraltar Airport, hasSafetyMeasure, road barriers for runway crossings]
  • A. measuresSafetyUsing
    Indicates that an entity evaluates or assesses safety by employing a specified method, tool, or standard.
  • B. safeguardingMeasuresInclude
    Indicates that certain specific protective or security measures are contained within, or form part of, a broader set of safeguarding measures.
  • C. hasSafetyInfrastructure chosen
    Indicates that appropriate safety-related structures, systems, or measures are present for the referenced entity or environment.
  • D. hasSafetyRegulationCompliance
    Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
  • E. safetyRequirement
    Indicates that one entity specifies or imposes conditions, standards, or measures necessary to ensure the safety of another entity or activity.
  • 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_69ab4b7cd13481909174bca9809ed259 completed March 6, 2026, 9:47 p.m.
NER Named-entity recognition batch_69abddceb9d88190961e30d521a21552 completed March 7, 2026, 8:11 a.m.
PD Predicate disambiguation batch_69abdd00b65c8190a8ea444308c4fa2b completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 9:57 p.m.