Triple
T2023622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Buck raids |
E44158
|
entity |
| Predicate | aircraftTypeRole |
P2860
|
FINISHED |
| Object | strategic 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: strategic bomber | Statement: [Black Buck raids, aircraftTypeRole, strategic bomber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aircraftTypeRole Context triple: [Black Buck raids, aircraftTypeRole, strategic bomber]
-
A.
primaryAircraftRole
chosen
Indicates the main operational function or mission type an aircraft is primarily designed or used to perform.
-
B.
aircraftType
Indicates the specific model or category of aircraft associated with an entity or event.
-
C.
usedByAircraftType
Indicates that something (such as equipment, infrastructure, or a procedure) is employed or operated by a specific type or category of aircraft.
-
D.
iataAircraftTypeCode
Indicates the standardized IATA code that specifies the aircraft type used in a flight or aviation context.
-
E.
aircraftTypesCarried
Indicates that one entity (typically a vessel, facility, or platform) carries or is capable of carrying specific types of aircraft as part of its operations or configuration.
- 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_69a8891201bc8190aca837be6de41579 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb8f1728481909ae36e821b9edef2 |
completed | March 7, 2026, 5:34 a.m. |
| PD | Predicate disambiguation | batch_69abb7a389408190a84a54856352f15b |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:38 p.m.