Triple
T11413923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geraldton Airport |
E270439
|
entity |
| Predicate | runway03/21Orientation |
P6272
|
FINISHED |
| Object | 030/210 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: 030/210 degrees | Statement: [Geraldton Airport, runway03/21Orientation, 030/210 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runway03/21Orientation Context triple: [Geraldton Airport, runway03/21Orientation, 030/210 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.
orientation
Indicates the relative directional alignment or facing of one entity with respect to another or to a reference frame.
-
D.
functionalOrientation
Indicates a relationship where an entity is characterized by the specific function, role, or operational purpose it is oriented or designed to fulfill.
-
E.
orientationType
Indicates the specific kind or category of orientation relationship that exists between entities (such as spatial, directional, or alignment-based orientation).
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801acd9bc81908a23b1b7b4e778d3 |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.