Triple
T2515590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trapani–Birgi Airport |
E55404
|
entity |
| Predicate | servesFlights |
P19814
|
FINISHED |
| Object | domestic flights |
—
|
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: domestic flights | Statement: [Trapani–Birgi Airport, servesFlights, domestic flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesFlights Context triple: [Trapani–Birgi Airport, servesFlights, domestic flights]
-
A.
servesAirport
Indicates that a transportation service or route provides access to and operates for a particular airport.
-
B.
hasScheduledFlights
chosen
Indicates that there are one or more flights planned and set to occur between the related entities according to a schedule.
-
C.
servesAirline
Indicates that a transportation facility or location provides service for, or is regularly used by, a specified airline.
-
D.
operatesFlightsTo
Indicates that one entity (typically an airline) runs or provides flight services to the location represented by the other entity.
-
E.
servesAirlineType
Indicates that a service provider (such as an airport, terminal, or facility) accommodates or operates flights for a specified type or category of airline.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0bf37c0819088d28b5081ba7556 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.