Triple
T29695475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fraport Twin Star Airport Management AD |
E751337
|
entity |
| Predicate | sharesBorderingAirportsRegion |
P195930
|
FINISHED |
| Object | Varna |
—
|
NE NERFINISHED |
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: Varna | Statement: [Fraport Twin Star Airport Management AD, sharesBorderingAirportsRegion, Varna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesBorderingAirportsRegion Context triple: [Fraport Twin Star Airport Management AD, sharesBorderingAirportsRegion, Varna]
-
A.
isBorderAirport
Indicates that an airport is located near or on a national or regional border, serving cross-border traffic or border-adjacent areas.
-
B.
sharesAirportWith
Indicates that two entities use or are associated with the same airport.
-
C.
hasRegionalAirport
Indicates that a place or region possesses or is served by a regional airport.
-
D.
associatedAirportICAOSubregion
Indicates a relationship where an airport is linked to the specific ICAO-defined subregion in which it is located or with which it is operationally associated.
-
E.
isMajorRegionalAirportFor
Indicates that an airport serves as a primary or significant air travel hub for a particular region.
- 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_69f0d6266f8481909e70bb41cda18587 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69fdf5d05cc481909ec9e1b1f0784279 |
completed | May 8, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69fdf0cdd6948190838864ab3120dfa6 |
completed | May 8, 2026, 2:18 p.m. |
| PDg | Predicate description generation | batch_69fdf5cfa1ec8190b80d887fa1bfb4cf |
completed | May 8, 2026, 2:40 p.m. |
Created at: April 28, 2026, 7:19 p.m.