Triple
T24004327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toscana Aeroporti |
E594329
|
entity |
| Predicate | hasIATACityCodeCoverage |
P114462
|
FINISHED |
| Object | FLR |
—
|
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: FLR | Statement: [Toscana Aeroporti, hasIATACityCodeCoverage, FLR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIATACityCodeCoverage Context triple: [Toscana Aeroporti, hasIATACityCodeCoverage, FLR]
-
A.
hasIATAcode
Indicates that an entity, typically a transportation facility like an airport, is associated with a specific IATA (International Air Transport Association) code.
-
B.
hasIATACityCodePair
Indicates that there is an association between two entities representing a pair of IATA city codes that are related in some defined way (e.g., as a linked or corresponding code pair).
-
C.
hasIataAirportCodeContext
chosen
Indicates that an entity is associated with a specific IATA airport code within a particular contextual scope or usage.
-
D.
hasIATAIndustryCode
Indicates that an entity is associated with a specific IATA industry code that classifies its role or function in the air transport industry.
-
E.
hasIATAStyle
Indicates that one entity uses or conforms to the IATA (International Air Transport Association) style or formatting standard associated with another 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_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.