Triple
T1114413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Force Training Command |
E11063
|
entity |
| Predicate | hasTrainingType |
P24513
|
FINISHED |
| Object | pilot 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: pilot training | Statement: [Air Force Training Command, hasTrainingType, pilot training]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrainingType Context triple: [Air Force Training Command, hasTrainingType, pilot training]
-
A.
requiresTraining
Indicates that one entity can only be properly or legitimately used, performed, or engaged with if the other entity has first received appropriate training.
-
B.
hasActivityType
Indicates the specific kind or category of activity associated with an entity or event.
-
C.
hasBeginnerFriendlyTraining
Indicates that an entity provides training or instructional resources suitable for beginners or those with little prior experience.
-
D.
trainedAs
Indicates that one entity has received education or instruction to perform the role, profession, or function represented by another entity.
-
E.
hasTrailType
Indicates that an entity (such as a trail or route) is associated with a specific type or category of trail.
- F. None of above. chosen
Provenance (4 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bbd7ff1881908c943ecdfea59e81 |
completed | March 1, 2026, 10:21 p.m. |
Created at: March 1, 2026, 7:43 p.m.