Triple
T37260515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Engels Air Base |
E924243
|
entity |
| Predicate | hasBomberType |
P196968
|
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: [Engels Air Base, hasBomberType, strategic bomber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBomberType Context triple: [Engels Air Base, hasBomberType, strategic bomber]
-
A.
hasBomber
Indicates that an entity possesses, controls, or is associated with a bomber aircraft.
-
B.
isBomber
Indicates that an entity functions as or is classified as a bomber, typically designed or used to deliver explosive ordnance.
-
C.
mainBomberAircraft
Indicates that an entity serves as the primary bomber aircraft used by another entity (such as a military force, operation, or country).
-
D.
hasBossType
Indicates that one entity functions as the superior or boss type in relation to another entity.
-
E.
hasBombBay
Indicates that an entity is equipped with or contains a bomb bay compartment for carrying and deploying bombs.
- F. None of above. chosen
Provenance (4 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_69f76eabd6c481909d414a80a1345c98 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
| PDg | Predicate description generation | batch_69fe6fe98e38819085100ce4c6cee5b8 |
completed | May 8, 2026, 11:21 p.m. |
Created at: May 3, 2026, 4:15 p.m.