Triple

T34298695
Position Surface form Disambiguated ID Type / Status
Subject Shelby–Cleveland County Regional Airport E880105 entity
Predicate has pushpin map region P101550 FINISHED
Object USA North Carolina NE NERFINISHED

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: USA North Carolina | Statement: [Shelby–Cleveland County Regional Airport, has pushpin map region, USA North Carolina]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: has pushpin map region
Context triple: [Shelby–Cleveland County Regional Airport, has pushpin map region, USA North Carolina]
  • A. hasMapRegion chosen
    Indicates that an entity is associated with, or belongs to, a specific geographic or logical map region.
  • B. pushpinMapCountry
    Indicates the country whose map is used as the background or reference area for placing a pushpin-style location marker.
  • C. mapRegion
    Indicates a relationship where a map or mapping system corresponds to, covers, or is associated with a specific geographic or logical region.
  • D. hasRegionCenter
    Indicates that a region is associated with a specific central point or location that serves as its geometric or administrative center.
  • E. hasRegion
    Indicates that an entity includes, contains, or is associated with a specific geographic or administrative region as part of its scope or structure.
  • 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_69f349b79f6c81909cb468c92c39c74d completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69f717836f0c8190b4a397bbac37dd09 completed May 3, 2026, 9:38 a.m.
PD Predicate disambiguation batch_69f7127a2ff08190b77d00963c9df621 completed May 3, 2026, 9:16 a.m.
Created at: May 1, 2026, 1:57 a.m.