Triple
T6273119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vágar Airport |
E140585
|
entity |
| Predicate | has navigation aid |
P8170
|
FINISHED |
| Object | instrument landing system |
—
|
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: instrument landing system | Statement: [Vágar Airport, has navigation aid, instrument landing system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has navigation aid Context triple: [Vágar Airport, has navigation aid, instrument landing system]
-
A.
hasNavigationAid
chosen
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
B.
isNavigationalAid
Indicates that one entity serves as a navigational aid or guide to help locate, orient, or move toward another entity or destination.
-
C.
navigationAidType
Indicates the specific kind or category of navigation aid associated with an entity.
-
D.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
E.
hasNavigationTechnology
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
- 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_69c008cc158881908df6ec94a911c736 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c063be5a148190a8752426d2d220f8 |
completed | March 22, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69c05606fb50819082d1a5a91e5030b6 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:25 p.m.