Triple
T27395794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 14/32 |
E691680
|
entity |
| Predicate | hasFAACodeAirport |
P420
|
FINISHED |
| Object | STS |
—
|
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: STS | Statement: [Runway 14/32, hasFAACodeAirport, STS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFAACodeAirport Context triple: [Runway 14/32, hasFAACodeAirport, STS]
-
A.
hasFAACode
Indicates that an entity is associated with a specific FAAC (Federal Aviation Administration Code) identifier.
-
B.
hasFAAField
Indicates that an entity possesses or is associated with an airfield that has an FAA-designated field identifier.
-
C.
hasIcaoAirport
Indicates that an entity is associated with an airport identified by a specific ICAO (International Civil Aviation Organization) airport code.
-
D.
hasAirportRelatedFunction
Indicates that something performs a role, service, or activity specifically related to the operation, support, or functioning of an airport.
-
E.
FAAcode
chosen
Indicates that an entity (such as an airport or facility) is associated with a specific identifying code assigned by the Federal Aviation Administration (FAA).
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 12:27 p.m.