Triple
T24004315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toscana Aeroporti |
E594329
|
entity |
| Predicate | operatesRunwaysAt |
P38515
|
FINISHED |
| Object | Florence Airport |
—
|
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: Florence Airport | Statement: [Toscana Aeroporti, operatesRunwaysAt, Florence Airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesRunwaysAt Context triple: [Toscana Aeroporti, operatesRunwaysAt, Florence Airport]
-
A.
hasRunwaysAt
Indicates that a location or facility possesses one or more runways situated at that place.
-
B.
isPrimaryRunwayOf
Indicates that a runway serves as the main or principal runway for a particular airport or airfield.
-
C.
runwaysUsableAt
Indicates that certain runways at a location are available and suitable for use (e.g., for takeoff or landing) at a given time or under specified conditions.
-
D.
operatesAirport
chosen
Indicates that one entity manages and runs the operations of an airport.
-
E.
hasRunwayOperations
Indicates that an entity conducts or is involved in operational activities on an airport runway, such as takeoffs, landings, or related ground movements.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d4681fd88190949c5c91d4f94910 |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:40 p.m.