Triple
T7751324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAN |
E175768
|
entity |
| Predicate | associatedWithRunwayConfiguration |
P15146
|
FINISHED |
| Object | single-runway 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: single-runway airport | Statement: [SAN, associatedWithRunwayConfiguration, single-runway airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithRunwayConfiguration Context triple: [SAN, associatedWithRunwayConfiguration, single-runway airport]
-
A.
hasRunwayConfiguration
chosen
Indicates a specific arrangement or setup of runways associated with an airport, airfield, or similar facility.
-
B.
hasRunwayConfigurationRole
Indicates that an entity plays a specific functional role within a particular runway configuration.
-
C.
hasRunwayApproachType
Indicates the specific type or category of approach procedure associated with a runway.
-
D.
hasRunwayOrientation
Indicates that a runway is aligned or oriented in a specific directional heading.
-
E.
isRunwayOf
Indicates that a physical runway is a component or facility belonging to, used by, or officially associated with a particular airport or airfield.
- 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_69c69960b3588190a53aa590d31d9544 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c705257ca08190a78c592a1e616da8 |
completed | March 27, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69c7016df2b08190b2330a2010691431 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:08 p.m.