Triple
T35656054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | So.G.Aer S.p.A. |
E1030286
|
entity |
| Predicate | servesCityThroughAirport |
P51581
|
FINISHED |
| Object | Cagliari |
—
|
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: Cagliari | Statement: [So.G.Aer S.p.A., servesCityThroughAirport, Cagliari]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesCityThroughAirport Context triple: [So.G.Aer S.p.A., servesCityThroughAirport, Cagliari]
-
A.
airportServesAs
Indicates that an airport functions in a particular role or capacity (such as primary, secondary, or hub) for a specified area, organization, or service.
-
B.
airportServed
Indicates that a particular airport provides service to, or is used for air travel to and from, a given location or area.
-
C.
associatedAirportServes
chosen
Indicates that a given airport provides service to, or is used by, the associated entity (such as a city, region, or facility).
-
D.
servesAirport
Indicates that a transportation service or route provides access to and operates for a particular airport.
-
E.
servesAirportIATA
Indicates that a transportation service or facility operates routes to or from the airport identified by the given IATA code.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a0019b0e9fc81909494320f05e81742 |
completed | May 10, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a00193379e0819096d1985686ce10e3 |
completed | May 10, 2026, 5:35 a.m. |
Created at: May 3, 2026, 4:05 p.m.