Triple
T25351989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Halifax Mk VII |
E635711
|
entity |
| Predicate | bombloadCategory |
P9817
|
FINISHED |
| Object | heavy bombload |
—
|
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: heavy bombload | Statement: [Halifax Mk VII, bombloadCategory, heavy bombload]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bombloadCategory Context triple: [Halifax Mk VII, bombloadCategory, heavy bombload]
-
A.
bombLoad
chosen
Indicates the amount or configuration of bombs carried by an entity, typically an aircraft, for a mission or operation.
-
B.
bombType
Indicates the specific kind or category of bomb associated with an event, object, or action.
-
C.
bombBay
Indicates that an entity serves as or is located in the bomb bay compartment of an aircraft, where bombs are stored and released.
-
D.
munitionWeightCategory
Indicates the classification of a munition based on its weight range or weight-related category.
-
E.
explosiveClass
Indicates the classification or category assigned to an explosive based on its type, properties, or regulatory class.
- 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_69e75a9ac5d881909387ed766e20cd47 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f49dfdd56481908fae2a1c59585725 |
completed | May 1, 2026, 12:35 p.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
Created at: April 21, 2026, 1:34 p.m.