Triple
T19282731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vlorë International Airport |
E482229
|
entity |
| Predicate | hasPlannedRunwaySurface |
P15527
|
FINISHED |
| Object | asphalt |
—
|
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: asphalt | Statement: [Vlorë International Airport, hasPlannedRunwaySurface, asphalt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedRunwaySurface Context triple: [Vlorë International Airport, hasPlannedRunwaySurface, asphalt]
-
A.
runwaySurface
Indicates the type or condition of the surface material that a runway is made of or covered with.
-
B.
runwayPlan
Indicates a planned or designated use of a runway for aircraft operations (such as takeoff, landing, or sequencing) within an airfield’s operational schedule.
-
C.
hasRunwayPresence
Indicates that an entity maintains a physical runway or landing strip suitable for aircraft operations.
-
D.
hasRunwayOrPad
Indicates that a location possesses a designated runway or launch/landing pad suitable for vehicle operations.
-
E.
hasRunwayType
chosen
Indicates that an airport or airfield has a runway of a specified type or surface classification.
- 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.