Triple

T18998849
Position Surface form Disambiguated ID Type / Status
Subject LIPZ E464890 entity
Predicate isInICAORegion P42294 FINISHED
Object L (Southern Europe) 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: L (Southern Europe) | Statement: [LIPZ, isInICAORegion, L (Southern Europe)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInICAORegion
Context triple: [LIPZ, isInICAORegion, L (Southern Europe)]
  • A. ICAORegion
    Indicates that an entity is located within, associated with, or governed by a specific ICAO (International Civil Aviation Organization) region.
  • B. appliesToAirspaceOf
    Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
  • C. isInNationalAirspaceSystem
    Indicates that an aircraft, flight, or operation is currently within the boundaries and regulatory scope of a country's National Airspace System.
  • D. aircraftPrimaryOperationalRegion
    Indicates the main geographic area or region in which an aircraft is primarily operated or intended to operate.
  • E. associatedAirportICAOSubregion chosen
    Indicates a relationship where an airport is linked to the specific ICAO-defined subregion in which it is located or with which it is operationally associated.
  • 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_69d8dd01a56c81909694a128c66b21d7 completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5d6838f4481909b265e29964b0dca completed April 20, 2026, 7:32 a.m.
PD Predicate disambiguation batch_69e4a2f88e0c81908cb20f08bf24cd32 completed April 19, 2026, 9:40 a.m.
Created at: April 10, 2026, 12:01 p.m.