Triple
T37059911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAC |
E917294
|
entity |
| Predicate | managesAirportInRegion |
P193097
|
FINISHED |
| Object | Sicily |
—
|
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: Sicily | Statement: [SAC, managesAirportInRegion, Sicily]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesAirportInRegion Context triple: [SAC, managesAirportInRegion, Sicily]
-
A.
primaryAirportManaged
Indicates that one entity is responsible for operating, overseeing, or administering another entity’s main or primary airport.
-
B.
airportLocationManaged
Indicates that the management or administrative control of an airport’s location is exercised by a particular authority or organization.
-
C.
isMajorRegionalAirportFor
Indicates that an airport serves as a primary or significant air travel hub for a particular region.
-
D.
servesAsPrimaryAirportOperatorForCity
Indicates that an entity functions as the main organization responsible for operating the primary airport serving a particular city.
-
E.
airportTypeManaged
Indicates that an entity is responsible for managing or overseeing a particular type or category of airport.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: May 3, 2026, 4:14 p.m.