Triple
T19282733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vlorë International Airport |
E482229
|
entity |
| Predicate | hasPlannedCategory |
P76632
|
FINISHED |
| Object | public use airport |
—
|
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: public use airport | Statement: [Vlorë International Airport, hasPlannedCategory, public use airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedCategory Context triple: [Vlorë International Airport, hasPlannedCategory, public use airport]
-
A.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
B.
hasCategories
Indicates that an entity is associated with one or more categories that classify or group it.
-
C.
hasCategoryOn
Indicates that something is assigned to or associated with a specific category within a given context or scope.
-
D.
hasPlannedPart
Indicates that one entity includes another entity as a component or segment within a planned or scheduled whole.
-
E.
categoryForPlanning
chosen
Indicates that something is assigned to a specific category used for organizing or structuring planning activities or processes.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbffda78819088bf8dbc61756831 |
completed | April 20, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69e4dd07a7208190afcd51ba1dc87c33 |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:30 p.m.