Triple
T27570944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saidu Sharif Airport |
E696031
|
entity |
| Predicate | hasNavigationCodeType |
P59303
|
FINISHED |
| Object | IATA |
—
|
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: IATA | Statement: [Saidu Sharif Airport, hasNavigationCodeType, IATA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNavigationCodeType Context triple: [Saidu Sharif Airport, hasNavigationCodeType, IATA]
-
A.
hasNavigationCode
chosen
Indicates that an entity is associated with a specific navigation code used to identify or guide its position, route, or access within a system or environment.
-
B.
hasNavigationClass
Indicates that an entity is assigned to, or associated with, a particular navigation-related classification or category.
-
C.
hasNavigationKey
Indicates that one entity serves as a navigation key or reference used to access, locate, or traverse to another related entity.
-
D.
hasNavigationUse
Indicates that something is used for navigation or serves a navigational function in relation to another entity.
-
E.
hasNavigationModel
Indicates that an entity is associated with or uses a specific navigation model that defines how it determines or follows routes or paths.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 27, 2026, 1:43 p.m.