Triple
T6372713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilatus Aircraft |
E143388
|
entity |
| Predicate | PC-21Role |
P9463
|
FINISHED |
| Object | advanced military 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: advanced military trainer | Statement: [Pilatus Aircraft, PC-21Role, advanced military trainer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PC-21Role Context triple: [Pilatus Aircraft, PC-21Role, advanced military trainer]
-
A.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
basedAircraftRole
Indicates that an aircraft is regularly stationed at a particular location in a specified operational role or function.
-
C.
roleInEngine
Indicates the specific function or responsibility an entity has within an engine or engine-like system.
-
D.
crewVariantName
Indicates the specific name or label assigned to a particular variant or version of a crew configuration.
-
E.
navalTacticRole
Indicates the specific tactical function or role an entity performs within a naval operation or maritime combat context.
- 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_69c008d9f4348190ab598a2913259a1c |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06829d76c819092b476631459233a |
completed | March 22, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69c060ee055081908c79a1d151bd74cd |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:33 p.m.