Triple
T27327399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 11L/29R |
E689692
|
entity |
| Predicate | partOfAirportType |
P193461
|
FINISHED |
| Object | public-use airport |
—
|
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: public-use airport | Statement: [Runway 11L/29R, partOfAirportType, public-use airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfAirportType Context triple: [Runway 11L/29R, partOfAirportType, public-use airport]
-
A.
isPartOfAirportLayout
Indicates that something is a component or element within the overall physical or functional layout of an airport.
-
B.
partOfAirportLocatedIn
Indicates that a specific part or component of an airport is geographically or administratively located within a particular area or region.
-
C.
airportTerminalArea
Indicates the spatial area or zone associated with an airport terminal.
-
D.
aircraftFacility
Indicates that a facility is designed, equipped, or used to support the operation, maintenance, or accommodation of aircraft.
-
E.
heliportType
Indicates the specific classification or category of a heliport based on its design, function, or operational characteristics.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69fd485e0c20819099756b4fe39ac326 |
completed | May 8, 2026, 2:20 a.m. |
Created at: April 27, 2026, 11:36 a.m.