Triple
T15376281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Education and Training Command |
E367675
|
entity |
| Predicate | formedAsMajorCommand |
P118512
|
FINISHED |
| Object | 1942 |
—
|
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: 1942 | Statement: [Air Education and Training Command, formedAsMajorCommand, 1942]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedAsMajorCommand Context triple: [Air Education and Training Command, formedAsMajorCommand, 1942]
-
A.
formerCommand
Indicates that one entity previously held command or leadership authority over another entity but no longer does.
-
B.
commandedAs
Indicates that one entity held authority over another and issued orders or directives to be carried out.
-
C.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
D.
commandedByFrom
Indicates that an entity is under the authority or control of another entity originating from a specified source or location.
-
E.
formationTypeCommanded
Indicates that an agent issues an order specifying the type of formation that another entity or group should adopt.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e5ece1081908d7c1289258b9c1f |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:18 a.m.