Triple
T29453650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICAO volcanic ash advisory format |
E747041
|
entity |
| Predicate | verticalReference |
P10733
|
FINISHED |
| Object | flight levels |
—
|
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: flight levels | Statement: [ICAO volcanic ash advisory format, verticalReference, flight levels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: verticalReference Context triple: [ICAO volcanic ash advisory format, verticalReference, flight levels]
-
A.
verticalLocation
Indicates a vertical positional relationship where one entity is located above or below another along the up-down axis.
-
B.
verticalOrder
Indicates that one entity is positioned directly above or below another along a vertical axis, establishing their relative vertical arrangement.
-
C.
verticalBandPosition
Indicates the relative vertical placement or ordering of a band or stripe within a larger layout or structure.
-
D.
targetVertical
Indicates that one entity is directed toward, aligned with, or intended for a specific vertical market, domain, or industry segment.
-
E.
verticalExtent
chosen
Indicates the total height or vertical span of an entity or region from its lowest to highest point.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b69acc08190b571a81fb53cf718 |
completed | May 2, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 3:34 p.m.