Triple
T29684485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VORTAC NSE |
E751046
|
entity |
| Predicate | navAidType |
P5538
|
FINISHED |
| Object | VOR/DME equivalent |
—
|
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: VOR/DME equivalent | Statement: [VORTAC NSE, navAidType, VOR/DME equivalent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navAidType Context triple: [VORTAC NSE, navAidType, VOR/DME equivalent]
-
A.
navigationAidType
chosen
Indicates the specific kind or category of navigation aid associated with an entity.
-
B.
navigationAidIdentifier
Indicates that an entity is assigned or associated with an identifier used to uniquely reference a specific navigation aid.
-
C.
isNavigationalAid
Indicates that one entity serves as a navigational aid or guide to help locate, orient, or move toward another entity or destination.
-
D.
airportNavigationAids
Indicates that an airport is equipped with specific navigation aids used to guide aircraft during approach, landing, or departure.
-
E.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6728e59f881909bcc0068f136ab11 |
completed | May 2, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69f6659f246081909821c5f452d14e8f |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:12 p.m.