Triple
T28932878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heinkel He 162 |
E733834
|
entity |
| Predicate | intendedPilotTrainingLevel |
P4144
|
FINISHED |
| Object | minimally trained pilots |
—
|
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: minimally trained pilots | Statement: [Heinkel He 162, intendedPilotTrainingLevel, minimally trained pilots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedPilotTrainingLevel Context triple: [Heinkel He 162, intendedPilotTrainingLevel, minimally trained pilots]
-
A.
trainingLevel
chosen
Indicates the degree or stage of training or skill development that an entity has attained.
-
B.
pilotRequirement
Indicates that a certain condition, qualification, or resource is required in order for a pilot to operate or perform a specified activity.
-
C.
hasFlightTrainingActivity
Indicates that an entity is involved in or associated with a flight training activity.
-
D.
aircraftRoleTrained
Indicates that an entity has been trained or qualified to perform a specific role or function on a particular type of aircraft.
-
E.
isPilot
Indicates that one entity serves as the pilot (operator in control of a vehicle or aircraft) for another entity.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7626667f48190ad90867eb67ec582 |
completed | May 3, 2026, 2:57 p.m. |
| PD | Predicate disambiguation | batch_69f76175d6608190b60b268e20f49ed9 |
completed | May 3, 2026, 2:53 p.m. |
Created at: April 28, 2026, 8:29 a.m.