Triple
T30866380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 12/30 |
E786211
|
entity |
| Predicate | runwayNumberEnd1 |
P8866
|
FINISHED |
| Object | 12 |
—
|
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: 12 | Statement: [Runway 12/30, runwayNumberEnd1, 12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runwayNumberEnd1 Context triple: [Runway 12/30, runwayNumberEnd1, 12]
-
A.
runwayEnd
Indicates that one entity represents the end point or terminus of a runway associated with the other entity.
-
B.
runwayEndHeading
Indicates the directional heading or bearing associated with the end of a runway, typically expressed in degrees relative to north.
-
C.
hasRunwayNumber
chosen
Indicates that an airport or airfield runway is assigned a specific identifying number.
-
D.
runwayUsedAs
Indicates that a particular runway is being utilized for a specific purpose, role, or operational function.
-
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_69f224b9df2c819086f55f8bcf7f382e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: April 29, 2026, 8:47 p.m.