Triple
T23121770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antonio José de Sucre Airport |
E576911
|
entity |
| Predicate | navigationAidIdentifier |
P150990
|
FINISHED |
| Object | CUM VOR-DME |
—
|
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: CUM VOR-DME | Statement: [Antonio José de Sucre Airport, navigationAidIdentifier, CUM VOR-DME]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navigationAidIdentifier Context triple: [Antonio José de Sucre Airport, navigationAidIdentifier, CUM VOR-DME]
-
A.
navigationAidType
Indicates the specific kind or category of navigation aid associated with an entity.
-
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.
hasNavigationAid
Indicates that one entity provides or is equipped with a navigation aid used to assist in determining position or direction.
-
D.
lighthouseName
Indicates that a lighthouse is identified by a specific name.
-
E.
GNISID
Indicates that an entity is associated with a specific identifier from the U.S. Geographic Names Information System (GNIS), uniquely linking it to an official geographic feature record.
- 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_69e245f6c2e881909a228fdcfeb7c7d3 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e50c500819095d59aef44388153 |
completed | April 29, 2026, 4:51 a.m. |
| PD | Predicate disambiguation | batch_69ef89f020588190b43393e048e7eda3 |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:59 p.m.