Triple
T5085326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riga International Airport |
E114621
|
entity |
| Predicate | offersSchengenFlights |
P33076
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Riga International Airport, offersSchengenFlights, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersSchengenFlights Context triple: [Riga International Airport, offersSchengenFlights, yes]
-
A.
supportsSchengenFlights
chosen
Indicates that an entity enables or accommodates flights operating within the Schengen Area.
-
B.
offersTours
Indicates that one entity provides or makes available guided tours or tour services to another entity.
-
C.
airlineService
Indicates that an airline operates transportation services (such as flights) between specified locations or for specified routes.
-
D.
offersClassOfTravel
Indicates that a service provider makes a particular class or tier of travel (e.g., economy, business, first) available as an option.
-
E.
supportsNonSchengenFlights
Indicates that the subject facility or service is capable of handling or accommodating flights that operate outside the Schengen Area.
- 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_69bd443e941881908eb4e8c685b6f656 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd751db4f4819088b998d7af0e6f41 |
completed | March 20, 2026, 4:26 p.m. |
| PD | Predicate disambiguation | batch_69bd7159adc881909effd4382c395c66 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:40 p.m.