Triple
T1329385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PZL-130 Orlik |
E28605
|
entity |
| Predicate | aircraftClass |
P1524
|
FINISHED |
| Object | subsonic trainer |
—
|
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: subsonic trainer | Statement: [PZL-130 Orlik, aircraftClass, subsonic trainer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftClass Context triple: [PZL-130 Orlik, aircraftClass, subsonic trainer]
-
A.
aircraftType
chosen
Indicates the specific model or category of aircraft associated with an entity or event.
-
B.
commonAircraftFamily
Indicates that two aircraft belong to the same aircraft family or series, sharing a common design lineage.
-
C.
carrierAircraft
Indicates that an aircraft is designed, equipped, or used to operate from an aircraft carrier.
-
D.
currentAircraftFamily
Indicates the specific family or series of aircraft that an entity is currently associated with or operating.
-
E.
planeNumber
Indicates that an entity is associated with a specific airplane identification number (such as a tail number or flight number).
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c30c948190afc6342b3dcda948 |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.