Triple
T5035804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Slam bomb |
E113416
|
entity |
| Predicate | usedAgainstTargetType |
P13821
|
FINISHED |
| Object | railway viaducts |
—
|
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: railway viaducts | Statement: [Grand Slam bomb, usedAgainstTargetType, railway viaducts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAgainstTargetType Context triple: [Grand Slam bomb, usedAgainstTargetType, railway viaducts]
-
A.
usesTarget
Indicates that one entity employs, applies, or operates on another entity as its target or object of action.
-
B.
supportsTargetType
Indicates that one entity is capable of operating with, handling, or being compatible with a specified target type.
-
C.
usedAgainst
chosen
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
D.
usedInType
Indicates that something serves as a component, element, or example within a particular type or category.
-
E.
usedInConflictType
Indicates that something (such as a resource, method, or capability) is employed or applied within a specific type or category of conflict.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73b9ad488190a2a8c4da8858eb91 |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.