Triple

T18214848
Position Surface form Disambiguated ID Type / Status
Subject Wayne County Airport E436124 entity
Predicate facilityRole P130272 FINISHED
Object local general aviation facility 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: local general aviation facility | Statement: [Wayne County Airport, facilityRole, local general aviation facility]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: facilityRole
Context triple: [Wayne County Airport, facilityRole, local general aviation facility]
  • A. facility
    Indicates that one entity is a building, installation, or physical infrastructure used to host, support, or enable the operations or activities of another entity.
  • B. facilityScope
    Indicates the extent or boundaries of responsibility, service, or operation associated with a particular facility.
  • C. facilityId
    Indicates a relationship that associates an entity with the unique identifier of the facility it belongs to or is located in.
  • D. servesFacility
    Indicates that one entity provides services or support to a particular facility as its client, target, or area of operation.
  • E. userFacility
    Indicates a relationship where a user is associated with, has access to, or operates within a particular facility.
  • 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_69d8b90dba6481908e119eb9aa4ca0cb completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4e476a6548190bda03190c5f531ad completed April 19, 2026, 2:19 p.m.
PD Predicate disambiguation batch_69e4332155d88190b106d0dceb4554af completed April 19, 2026, 1:42 a.m.
PDg Predicate description generation batch_69e438f684e48190b38c64b58c518b6a completed April 19, 2026, 2:07 a.m.
Created at: April 10, 2026, 10:32 a.m.