Triple
T10875563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class D airspace |
E256788
|
entity |
| Predicate | classificationLetter |
P96177
|
FINISHED |
| Object | D |
—
|
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: D | Statement: [Class D airspace, classificationLetter, D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: classificationLetter Context triple: [Class D airspace, classificationLetter, D]
-
A.
classified
Indicates that one entity has assigned another entity to a specific category, group, or type based on defined criteria.
-
B.
classificationStart
Indicates the point in time or process at which a classification or categorization of an entity begins.
-
C.
classificationIntroduced
Indicates that one entity has introduced or established a particular classification or categorization for another entity.
-
D.
classificationNote
Indicates a note or comment providing additional information or clarification about how something has been classified.
-
E.
classificationLevel
Indicates the degree or tier within an ordered system or hierarchy to which something is assigned for categorization or control purposes.
- 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_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. |
| PDg | Predicate description generation | batch_69d7101c96708190808fef73199e8482 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:21 p.m.