Triple
T27136832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Antwerp International Airport |
E681709
|
entity |
| Predicate | hasBusinessAviation |
P110600
|
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: [Antwerp International Airport, hasBusinessAviation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBusinessAviation Context triple: [Antwerp International Airport, hasBusinessAviation, true]
-
A.
hasCorporateAviation
chosen
Indicates that an entity operates, owns, or utilizes aircraft or aviation services for corporate or business purposes.
-
B.
hasGeneralAviationActivity
Indicates that an entity is involved in or supports non-commercial, private, or recreational aviation operations.
-
C.
servesAviationType
Indicates that one entity provides services or functions specifically for a particular type or category of aviation.
-
D.
hasRoleInAviation
Indicates that an entity holds or has held a specific role, position, or function within the field of aviation.
-
E.
hasAviationTheme
Indicates that something is characterized by or designed around elements related to aviation, such as aircraft, flying, or air travel.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 9:07 a.m.