Triple
T5957388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeroporto di Roma–Fiumicino |
E132549
|
entity |
| Predicate | hasSchengenAreaFacilities |
P33077
|
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: [Aeroporto di Roma–Fiumicino, hasSchengenAreaFacilities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSchengenAreaFacilities Context triple: [Aeroporto di Roma–Fiumicino, hasSchengenAreaFacilities, yes]
-
A.
hasSchengenArea
Indicates that a place, country, or region is part of, or included within, the Schengen Area for border-free movement.
-
B.
supportsSchengenFlights
Indicates that an entity enables or accommodates flights operating within the Schengen Area.
-
C.
supportsNonSchengenFlights
chosen
Indicates that the subject facility or service is capable of handling or accommodating flights that operate outside the Schengen Area.
-
D.
hasDutyFreeArea
Indicates that one entity provides or contains a designated duty-free area for another entity or for certain activities.
-
E.
hasTourismRestriction
Indicates that there is a limitation, prohibition, or special condition affecting tourism-related activities or access in relation to the referenced entity.
- 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_69c0086b05cc8190a8f36a96927a525c |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:02 p.m.