Triple
T1487700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avro Lancaster |
E29504
|
entity |
| Predicate | bombloadCapacity |
P9817
|
FINISHED |
| Object | up to 14,000 kg |
—
|
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: up to 14,000 kg | Statement: [Avro Lancaster, bombloadCapacity, up to 14,000 kg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bombloadCapacity Context triple: [Avro Lancaster, bombloadCapacity, up to 14,000 kg]
-
A.
ammunitionCapacity
Indicates the maximum amount of ammunition that something (typically a weapon or container) is designed to hold at one time.
-
B.
bombLoad
chosen
Indicates the amount or configuration of bombs carried by an entity, typically an aircraft, for a mission or operation.
-
C.
ammunitionType
Indicates the specific kind or category of ammunition associated with or used by an entity.
-
D.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
E.
bombTonnageDropped
Indicates the total weight of bombs that were released or deployed in a given event 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.