Triple
T997445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 111 Squadron RAF |
E21525
|
entity |
| Predicate | dutyDuringBattleOfBritain |
P19660
|
FINISHED |
| Object | day fighter operations |
—
|
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: day fighter operations | Statement: [No. 111 Squadron RAF, dutyDuringBattleOfBritain, day fighter operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dutyDuringBattleOfBritain Context triple: [No. 111 Squadron RAF, dutyDuringBattleOfBritain, day fighter operations]
-
A.
commandingOfficerBritishSide
Indicates that one entity serves as the commanding officer of another entity on the British side in a military context.
-
B.
statusDuringWorldWarII
chosen
Indicates the role, condition, or classification an entity had specifically during the period of World War II.
-
C.
primaryBritishFighterAircraft
Indicates that an aircraft serves as the main or most important fighter aircraft used by British military forces.
-
D.
statusDuringWar
Indicates the role, condition, or classification an entity held specifically during a period of war.
-
E.
commanderOfRAF
Indicates that one entity serves as the commander or head of the Royal Air Force in relation to 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_69a493c476b48190b41fc5e793171cc6 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4e0f0d081908b888c246d001786 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b057c48190b9e42df9246b3757 |
completed | March 1, 2026, 9:42 p.m. |
Created at: March 1, 2026, 7:41 p.m.