Triple
T24016712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Runway 05/23 |
E594695
|
entity |
| Predicate | designedToAccommodate |
P154879
|
FINISHED |
| Object | prevailing winds at Tiree 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: prevailing winds at Tiree Airport | Statement: [Runway 05/23, designedToAccommodate, prevailing winds at Tiree Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedToAccommodate Context triple: [Runway 05/23, designedToAccommodate, prevailing winds at Tiree Airport]
-
A.
designedToEmbark
Indicates that something is created or configured with the specific purpose of beginning or initiating a journey, process, or undertaking.
-
B.
designedToWithstand
Indicates that something has been intentionally created or engineered to resist, endure, or remain functional under specified conditions, forces, or stresses.
-
C.
designedForHighCapacity
Indicates that something is intentionally created or configured to handle a large volume, load, or throughput.
-
D.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
E.
designedToPlace
Indicates that something is intentionally created or configured for the purpose of positioning or setting another entity in a specific place or arrangement.
- F. None of above. chosen
Provenance (4 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d5a3f5a08190b7170270c4fcf080 |
completed | April 29, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:42 p.m.