Triple
T12585811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Air Ministry Specification B.12/36 |
E300457
|
entity |
| Predicate | aircraftTypeRequired |
P72991
|
FINISHED |
| Object | land-based bomber |
—
|
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: land-based bomber | Statement: [Air Ministry Specification B.12/36, aircraftTypeRequired, land-based bomber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftTypeRequired Context triple: [Air Ministry Specification B.12/36, aircraftTypeRequired, land-based bomber]
-
A.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
B.
aircraftRoleRequired
chosen
Indicates that a specific operational role or function is required of an aircraft within a given context or mission.
-
C.
intendedAircraft
Indicates that an aircraft is the one planned or designated to be used for a particular flight, mission, or operation.
-
D.
poweredAircraftType
Indicates that one entity is a type or category of aircraft that is propelled by an onboard power source (e.g., engines), as opposed to being unpowered.
-
E.
iataAircraftTypeCode
Indicates the standardized IATA code that specifies the aircraft type used in a flight or aviation 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:04 p.m.