Triple
T36420477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Cross to Guy Gibson |
E897138
|
entity |
| Predicate | associatedInnovation |
P76078
|
FINISHED |
| Object | use of bouncing bomb |
—
|
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: use of bouncing bomb | Statement: [Victoria Cross to Guy Gibson, associatedInnovation, use of bouncing bomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedInnovation Context triple: [Victoria Cross to Guy Gibson, associatedInnovation, use of bouncing bomb]
-
A.
associatedWithProductInnovation
Indicates a relationship where an entity is linked or connected to the development, introduction, or improvement of a product.
-
B.
associatedIdea
Indicates that one entity is conceptually linked or related to another as an idea, theme, or notion.
-
C.
hasInnovationType
Indicates that an entity is associated with, or classified by, a specific type or category of innovation.
-
D.
innovationArea
Indicates the thematic or domain-specific field in which an innovation is focused or applied.
-
E.
usedInnovation
chosen
Indicates that one entity applied or implemented an innovation (such as a new idea, method, or technology) 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_69f76e559b10819099d6655a6e14587c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.