Triple
T37059910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAC |
E917294
|
entity |
| Predicate | managesAirportInCity |
P115936
|
FINISHED |
| Object | Catania |
—
|
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: Catania | Statement: [SAC, managesAirportInCity, Catania]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managesAirportInCity Context triple: [SAC, managesAirportInCity, Catania]
-
A.
isLocatedAtAirportServingCity
Indicates that something is situated at an airport that provides service to a particular city.
-
B.
servesAsPrimaryAirportOperatorForCity
chosen
Indicates that an entity functions as the main organization responsible for operating the primary airport serving a particular city.
-
C.
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.
-
D.
primaryAirportManaged
Indicates that one entity is responsible for operating, overseeing, or administering another entity’s main or primary airport.
-
E.
basedInAirport
Indicates that an entity has its primary location, operations, or headquarters situated at a specific airport.
- 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd35d108908190b79b1e8e6bbd62aa |
completed | May 8, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69fd34cb46108190b43c3b7f67ec4cd4 |
completed | May 8, 2026, 12:56 a.m. |
Created at: May 3, 2026, 4:14 p.m.