Triple
T15755244
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeltweg |
E381950
|
entity |
| Predicate | airBaseType |
P46848
|
FINISHED |
| Object | Austrian Air Force base |
—
|
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: Austrian Air Force base | Statement: [Zeltweg, airBaseType, Austrian Air Force base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airBaseType Context triple: [Zeltweg, airBaseType, Austrian Air Force base]
-
A.
isAirBase
chosen
Indicates that the subject entity functions as a military air base, i.e., a facility used for operating, housing, and supporting aircraft and related activities.
-
B.
usesAirbaseType
Indicates that one entity makes use of, operates from, or is otherwise functionally associated with a particular type or category of airbase.
-
C.
airBaseOperator
Indicates that one entity operates, manages, or is responsible for running an air base used for aviation activities.
-
D.
usesAirbase
Indicates that one entity operates from, accesses, or conducts activities at a particular airbase.
-
E.
airLegBaseType
Indicates a basic type classification for a segment (leg) of an air journey within a larger travel or itinerary structure.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e05031f6a08190bfb333eced0a59a1 |
completed | April 16, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69e00531e7ac8190a4190cce4f7fab4c |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:47 a.m.