Triple
T5035738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tallboy bomb |
E113415
|
entity |
| Predicate | explosiveFillingMass |
P49453
|
FINISHED |
| Object | approximately 5,200 pounds |
—
|
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: approximately 5,200 pounds | Statement: [Tallboy bomb, explosiveFillingMass, approximately 5,200 pounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: explosiveFillingMass Context triple: [Tallboy bomb, explosiveFillingMass, approximately 5,200 pounds]
-
A.
explosiveFillerMass
chosen
Indicates the amount of explosive material contained within an object or device.
-
B.
explosiveMaterialUsed
Indicates that an explosive material was employed or involved in carrying out a particular action or event.
-
C.
estimatedAmmoniumNitrateMass
Indicates the estimated quantity or mass of ammonium nitrate associated with an entity or event.
-
D.
explosiveDevice
Indicates the presence or involvement of an object designed to explode or cause an explosion in relation to the associated entities.
-
E.
explosiveYieldApprox
Indicates that one entity has an approximate explosive yield value, typically expressing the estimated magnitude of an explosion or explosive device.
- 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.