Triple
T350004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal Air Force Bomber Command |
E7420
|
entity |
| Predicate | notableCommanderEnd |
P11104
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Royal Air Force Bomber Command, notableCommanderEnd, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableCommanderEnd Context triple: [Royal Air Force Bomber Command, notableCommanderEnd, 1945]
-
A.
notableCommanderAllies
Indicates that the subject commander has notable allied commanders with whom they are significantly associated or have cooperated.
-
B.
notableCommanderAxis
Indicates that the subject entity had a notable military commander role or position on the Axis side in a conflict or war.
-
C.
opposingCommander
Indicates that one entity serves as the commanding officer of a force that is in opposition or conflict with the force commanded by another entity.
-
D.
hasCommander
Indicates that one entity serves as the commanding officer or leader of another entity.
-
E.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb1f028c819098fa6480b4ca5cf0 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e955d1f88190bd687c46fa7c5469 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea60e590819081779a6510918d9b |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.