Triple
T5966720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Königsberg |
E132770
|
entity |
| Predicate | sovietAircraft |
P10178
|
FINISHED |
| Object | over 2000 aircraft |
—
|
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: over 2000 aircraft | Statement: [Battle of Königsberg, sovietAircraft, over 2000 aircraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovietAircraft Context triple: [Battle of Königsberg, sovietAircraft, over 2000 aircraft]
-
A.
developedAircraft
Indicates that an entity (such as a person or organization) was responsible for designing, creating, or engineering a particular aircraft.
-
B.
SovietDesignation
Indicates that an entity has been assigned an official designation or code name by Soviet authorities or according to Soviet classification systems.
-
C.
SovietEquipmentLosses
chosen
Indicates the extent or instances of military equipment lost by Soviet forces in a given conflict or period.
-
D.
Tu-95MSRole
Indicates the specific operational role or mission type assigned to the Tu-95MS aircraft within its usage or deployment context.
-
E.
mainFighterAircraft
Indicates that an aircraft serves as the primary fighter aircraft for a given country, organization, or military force.
- 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_69c0086c2364819091e9fe2f58fa2517 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c03fb7f8a88190a8bd45208bda4a03 |
completed | March 22, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69c0335a635881909c58c1ef0f97f1e8 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4:03 p.m.