Triple
T35983908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OIMM |
E1040653
|
entity |
| Predicate | associatedAirportHasCargoOperations |
P207124
|
FINISHED |
| Object | true |
—
|
LITERAL FINISHED |
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: true | Statement: [OIMM, associatedAirportHasCargoOperations, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedAirportHasCargoOperations Context triple: [OIMM, associatedAirportHasCargoOperations, true]
-
A.
isCargoAirportCode
Indicates that an airport code specifically designates an airport primarily used for cargo operations.
-
B.
hasAircraftOperationsType
Indicates the specific category or type of aircraft operations associated with an entity, such as commercial, military, or private use.
-
C.
servesAsPrimaryAirportOperatorForCity
Indicates that an entity functions as the main organization responsible for operating the primary airport serving a particular city.
-
D.
isMajorCargoAirport
Indicates that an airport primarily handles large volumes of cargo traffic and serves as a significant freight hub.
-
E.
hasCargoAirline
Indicates that one entity operates as a cargo airline for, or provides cargo air transport services to, another entity.
- 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_69f76e28293c8190ae3f4e2208b87117 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c82179081908325a59b8539b3a8 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:07 p.m.