Triple
T8476571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leipzig/Halle Airport |
E200407
|
entity |
| Predicate | hasNightFlightOperations |
P36720
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Leipzig/Halle Airport, hasNightFlightOperations, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNightFlightOperations Context triple: [Leipzig/Halle Airport, hasNightFlightOperations, yes]
-
A.
operatesNightFlights
chosen
Indicates that an entity conducts or provides flight operations during nighttime hours.
-
B.
hasRunwayOperations
Indicates that an entity conducts or is involved in operational activities on an airport runway, such as takeoffs, landings, or related ground movements.
-
C.
hasAircraftOperationsType
Indicates the specific category or type of aircraft operations associated with an entity, such as commercial, military, or private use.
-
D.
hasGeneralAviationActivity
Indicates that an entity is involved in or supports non-commercial, private, or recreational aviation operations.
-
E.
closedForFlightOperations
Indicates that a location, facility, or area is temporarily unavailable or prohibited for conducting flight operations.
- 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe51e21548190811e3c7ba7b196e5 |
completed | March 31, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.