Triple
T23593866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No. 214 Squadron RAF |
E582558
|
entity |
| Predicate | worldWarIIActivity |
P23985
|
FINISHED |
| Object | strategic bombing operations over Europe |
—
|
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: strategic bombing operations over Europe | Statement: [No. 214 Squadron RAF, worldWarIIActivity, strategic bombing operations over Europe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldWarIIActivity Context triple: [No. 214 Squadron RAF, worldWarIIActivity, strategic bombing operations over Europe]
-
A.
worldWarIIEntry
Indicates that an entity’s formal involvement or entry into World War II is being asserted in relation to a specific time, event, or condition.
-
B.
sideInWorldWarII
Indicates that an entity was aligned with or participated on a particular side during World War II.
-
C.
WWIIEvent
chosen
Indicates that the event is part of, or directly related to, the historical period and activities of World War II.
-
D.
WWIITheater
Indicates the geographic or operational theater in which a World War II-related event, action, or entity was involved.
-
E.
enemyDuringWWII
Indicates that one entity was an enemy of the other during World War II.
- 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_69e248f9e0a08190814772847003b1ff |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b08d63dc81908c092a87cf61f2b9 |
completed | April 29, 2026, 7:17 a.m. |
| PD | Predicate disambiguation | batch_69f118c96a0081908a8ac98ef7e7e60c |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:42 p.m.