Triple
T622331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Air Force Fighter Command |
E14539
|
entity |
| Predicate | commanderDuring |
P1197
|
FINISHED |
| Object | Hugh Dowding, Battle of Britain |
—
|
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: Hugh Dowding, Battle of Britain | Statement: [Royal Air Force Fighter Command, commanderDuring, Hugh Dowding, Battle of Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderDuring Context triple: [Royal Air Force Fighter Command, commanderDuring, Hugh Dowding, Battle of Britain]
-
A.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
-
B.
hasCommander
chosen
Indicates that one entity serves as the commanding officer or leader of another entity.
-
C.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
D.
commanderAttacker
Indicates that one entity serves as the commanding officer or leader of another entity that is acting as the attacker in a conflict or operation.
-
E.
commanderForDefender
Indicates that an entity serves as the commanding officer or leader responsible for directing and overseeing a defending force or defender.
- 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_69a4934b17c881909ace8270e8ddd202 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e402d9c8190936896e3ebb6edc5 |
completed | March 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69a49d0069d0819087c83b608f6fc053 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.