Triple
T10875557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class D airspace |
E256788
|
entity |
| Predicate | typicalLateralBoundary |
P84052
|
FINISHED |
| Object | cylinder around the 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: cylinder around the airport | Statement: [Class D airspace, typicalLateralBoundary, cylinder around the airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLateralBoundary Context triple: [Class D airspace, typicalLateralBoundary, cylinder around the airport]
-
A.
typicalBoundary
chosen
Indicates that one entity serves as the usual or characteristic boundary or limit for another entity.
-
B.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
C.
climateBoundaryBetween
Indicates a boundary or dividing line between two regions that differ in climate characteristics or classifications.
-
D.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
-
E.
easternBoundaryFormedBy
Indicates that the eastern boundary of an area, region, or object is defined or formed by a specified feature or entity.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7518a1db08190abf0c524b81487fa |
completed | April 9, 2026, 7:13 a.m. |
| PD | Predicate disambiguation | batch_69d70d360c388190a3d829fe8862434f |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.