Triple
T10875556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class D airspace |
E256788
|
entity |
| Predicate | symbolizedOnChartsAs |
P96176
|
FINISHED |
| Object | dashed blue line in the United States |
—
|
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: dashed blue line in the United States | Statement: [Class D airspace, symbolizedOnChartsAs, dashed blue line in the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolizedOnChartsAs Context triple: [Class D airspace, symbolizedOnChartsAs, dashed blue line in the United States]
-
A.
tickerSymbol
Indicates the association between a financial instrument or company and its unique abbreviated code used for trading on a securities exchange.
-
B.
symbolizedIn
Indicates that one entity serves as a symbol or representation of another entity.
-
C.
symbolizes
Indicates that one entity stands for, represents, or is used as a sign for another entity, concept, or idea.
-
D.
typicalSymbol
Indicates that something serves as a characteristic or commonly recognized symbol representing something else.
-
E.
symbolText
Indicates that a symbol is associated with or represented by a specific piece of text.
- 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.