Triple
T32594961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilde Sau tactic |
E833176
|
entity |
| Predicate | introducedDuringEvent |
P8259
|
FINISHED |
| Object | RAF Bomber Command offensive over Germany |
—
|
NE NERFINISHED |
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: RAF Bomber Command offensive over Germany | Statement: [Wilde Sau tactic, introducedDuringEvent, RAF Bomber Command offensive over Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedDuringEvent Context triple: [Wilde Sau tactic, introducedDuringEvent, RAF Bomber Command offensive over Germany]
-
A.
introducedDuring
chosen
Indicates that one entity was first brought into existence, use, or awareness within the time period, event, or context specified by the other entity.
-
B.
introducedEvent
Indicates that an entity is responsible for bringing an event into existence or initiating it for the first time.
-
C.
introducedForEventInCountry
Indicates that something was introduced specifically for an event that took place in a particular country.
-
D.
introducedForEventInCity
Indicates that something or someone was introduced specifically for an event that took place in a particular city.
-
E.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: May 1, 2026, 1:05 a.m.