Triple
T11441494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fayetteville Regional Airport |
E271154
|
entity |
| Predicate | runway4_22Orientation |
P6272
|
FINISHED |
| Object | 040/220 degrees |
—
|
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: 040/220 degrees | Statement: [Fayetteville Regional Airport, runway4_22Orientation, 040/220 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runway4_22Orientation Context triple: [Fayetteville Regional Airport, runway4_22Orientation, 040/220 degrees]
-
A.
hasRunwayOrientation
chosen
Indicates that a runway is aligned or oriented in a specific directional heading.
-
B.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an airport or airfield.
-
C.
runwayPair
Indicates that two runways are associated or grouped together as a functional pair, typically for coordinated or complementary use.
-
D.
isRunwayOf
Indicates that a physical runway is a component or facility belonging to, used by, or officially associated with a particular airport or airfield.
-
E.
runwayCharacteristic
Indicates a relationship where specific attributes or features are associated with a runway.
- 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_69d6aadeef688190874bcecd88b3dd9b |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d808891b7481908bf5a80cb7644061 |
completed | April 9, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69d7e7162b288190a0bfb89f7eb747c7 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:35 p.m.