Triple
T10517377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class B airspace |
E248068
|
entity |
| Predicate | hasCallSignPrefix |
P94340
|
FINISHED |
| Object | Class B associated primary airport identifier |
—
|
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: Class B associated primary airport identifier | Statement: [Class B airspace, hasCallSignPrefix, Class B associated primary airport identifier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCallSignPrefix Context triple: [Class B airspace, hasCallSignPrefix, Class B associated primary airport identifier]
-
A.
hasCallsignPrefixRole
Indicates that an entity has a specific role associated with a given callsign prefix.
-
B.
hasCallSignOwner
Indicates that a particular call sign is owned or assigned to a specific entity.
-
C.
supportsCallSign
Indicates that one entity is capable of recognizing, handling, or operating using a specified call sign.
-
D.
hasCallsignCompanion
Indicates that one entity serves as a companion or associated partner to another entity’s callsign.
-
E.
hasSignagePrefix
Indicates that one signage element begins with or contains another signage element as its initial segment or prefix.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509cd0fb8819087de2f9a93bad6e6 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb94fa10819091f585bab4379c6f |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe06d4a48190b1a45dd1d4e16df0 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:28 p.m.