Triple
T29703472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 13/31 |
E751556
|
entity |
| Predicate | hasFaaAirport |
P174250
|
FINISHED |
| Object | SNS |
—
|
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: SNS | Statement: [Runway 13/31, hasFaaAirport, SNS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFaaAirport Context triple: [Runway 13/31, hasFaaAirport, SNS]
-
A.
hasFAAField
chosen
Indicates that an entity possesses or is associated with an airfield that has an FAA-designated field identifier.
-
B.
hasAirportWithinJurisdiction
Indicates that a governing authority or administrative region has legal or administrative control over an airport located within its boundaries.
-
C.
hasIcaoAirport
Indicates that an entity is associated with an airport identified by a specific ICAO (International Civil Aviation Organization) airport code.
-
D.
hasAirportAccessTo
Indicates that one location or entity has direct access to another via an airport connection or service.
-
E.
isInFAARegion
Indicates that one entity (typically a location, airspace, or facility) lies within the jurisdictional area or region defined by the FAA (Federal Aviation Administration).
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: April 28, 2026, 7:25 p.m.