Triple
T5527398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kosciuszko Squadron |
E144952
|
entity |
| Predicate | typeOfAviationUnit |
P24170
|
FINISHED |
| Object | fighter aviation unit |
—
|
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: fighter aviation unit | Statement: [Kosciuszko Squadron, typeOfAviationUnit, fighter aviation unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAviationUnit Context triple: [Kosciuszko Squadron, typeOfAviationUnit, fighter aviation unit]
-
A.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
B.
isAviationElementFor
Indicates that something serves as an aviation-related component, feature, or element specifically associated with or used for a particular object, system, or context.
-
C.
aerialUnit
chosen
Indicates that the related entity functions as or is classified as an aerial unit, typically operating or acting in the air rather than on the ground or sea.
-
D.
iataAircraftTypeCode
Indicates the standardized IATA code that specifies the aircraft type used in a flight or aviation context.
-
E.
hasAirfieldType
Indicates that an airfield is classified as having a particular type or category of airfield.
- 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_69c008f873a481909b4d9f7e2db3c37d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f8a34a48190bcbd0036f79246a9 |
completed | March 22, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69c01b0a06348190b39ac9fe80d2836a |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:34 p.m.