Triple

T2764537
Position Surface form Disambiguated ID Type / Status
Subject KLGA E61302 entity
Predicate hasLimited P99 FINISHED
Object international flights 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: international flights | Statement: [KLGA, hasLimited, international flights]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLimited
Context triple: [KLGA, hasLimited, international flights]
  • A. hasLimitation chosen
    Indicates that an entity is subject to a constraint, restriction, or boundary that limits its scope, capability, or applicability.
  • B. isLimitOf
    Indicates that one quantity, function, or sequence approaches a particular value as its input or index approaches some specified point or condition.
  • C. hasLimitedAuthorityOver
    Indicates that one entity holds a constrained or partial power to direct, control, or make decisions about another entity, but not full or unrestricted authority.
  • D. hasLimitedParticipation
    Indicates that an entity is involved in an activity, event, or process only to a restricted or constrained extent, rather than with full participation.
  • E. gLimit
    Indicates a constraint or maximum boundary imposed on the magnitude, rate, or extent of something within a given context.
  • 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_69ab4b7bab6c8190a5c2efef19a8ef34 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_69abdcfc5e1c8190a5ac2c48d3eaeb0a completed March 7, 2026, 8:08 a.m.
Created at: March 6, 2026, 9:57 p.m.