Triple
T31729977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Augustine Airport |
E809833
|
entity |
| Predicate | runway13_31Orientation |
P6272
|
FINISHED |
| Object | 130/310 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: 130/310 degrees | Statement: [St. Augustine Airport, runway13_31Orientation, 130/310 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runway13_31Orientation Context triple: [St. Augustine Airport, runway13_31Orientation, 130/310 degrees]
-
A.
runway13_31Usage
Indicates how runway 13/31 is used, such as the type, frequency, or conditions of its operational usage.
-
B.
hasRunwayOrientation
chosen
Indicates that a runway is aligned or oriented in a specific directional heading.
-
C.
runway12_30Usage
Indicates the use or operational status of runway 12/30 for aircraft movements or related airport activities.
-
D.
runway03_21Use
Indicates use or operational status of runway 03/21 for aircraft movements or related airport activities.
-
E.
runway
Indicates a relationship where a runway serves as the takeoff and landing surface used by aircraft at an 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_69f348e0e4908190a884582eca646fb7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 30, 2026, 11:21 p.m.