Triple
T890071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folland Gnat T.1 |
E19218
|
entity |
| Predicate | trainingCategory |
P7752
|
FINISHED |
| Object | advanced flying training |
—
|
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 flying training | Statement: [Folland Gnat T.1, trainingCategory, advanced flying training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainingCategory Context triple: [Folland Gnat T.1, trainingCategory, advanced flying training]
-
A.
trainingFormat
Indicates the specific method or medium through which training is delivered or conducted.
-
B.
trainingSystem
Indicates a system or framework used to train, instruct, or develop skills or knowledge in a target entity.
-
C.
training
Indicates that one entity is teaching, coaching, or otherwise helping another entity acquire or improve a skill, behavior, or capability.
-
D.
courseType
chosen
Indicates the classification or category of a course based on its nature, level, or instructional format.
-
E.
typicalTraining
Indicates that an entity commonly undergoes or is associated with a standard or usual form of training in relation to another entity or 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_69a4939d37188190848be3d426ebc9ae |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ad0086a081908c47c285896a1f3c |
completed | March 1, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69a4aa9372e88190b5a9db4afdc045c6 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.