Triple
T38059669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish UIR |
E950304
|
entity |
| Predicate | ifrRequired |
P96240
|
FINISHED |
| Object | yes for most of the airspace |
—
|
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: yes for most of the airspace | Statement: [Scottish UIR, ifrRequired, yes for most of the airspace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ifrRequired Context triple: [Scottish UIR, ifrRequired, yes for most of the airspace]
-
A.
requiresForIFR
chosen
Indicates that one entity must be present, satisfied, or fulfilled in order for another entity to be valid or operable under Instrument Flight Rules (IFR).
-
B.
fallbackRequirement
Indicates a secondary or backup condition that applies when the primary requirement cannot be met.
-
C.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
D.
requiresInitiationIn
Indicates that one entity must be initiated, started, or activated within the context, scope, or environment defined by another entity.
-
E.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fc44c7e73c819082d4fc1900fb9632 |
completed | May 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69fbc8efffbc8190a139798ad1880526 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 3, 2026, 4:21 p.m.