Triple
T1487713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avro Lancaster |
E29504
|
entity |
| Predicate | roleInDambustersRaid |
P9463
|
FINISHED |
| Object | carried specially modified bouncing bombs |
—
|
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: carried specially modified bouncing bombs | Statement: [Avro Lancaster, roleInDambustersRaid, carried specially modified bouncing bombs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInDambustersRaid Context triple: [Avro Lancaster, roleInDambustersRaid, carried specially modified bouncing bombs]
-
A.
commanderOfRAF
Indicates that one entity serves as the commander or head of the Royal Air Force in relation to another entity.
-
B.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
C.
worldWarIIRole
Indicates the specific role, position, or function an entity had in relation to World War II.
-
D.
roleAtPearlHarbor
Indicates the specific role, position, or function an entity held in relation to the events at Pearl Harbor.
-
E.
JapaneseAirCommander
Indicates that one entity serves as a Japanese air force commander in relation to another entity or context.
- 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_69a498da82e08190ba833330d05f380f |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c6a44efc819084254614d8ea4669 |
completed | March 1, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69a4c486eacc81909c272f9bdf50a7c3 |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:12 p.m.