Triple
T5966719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Königsberg |
E132770
|
entity |
| Predicate | sovietArtilleryPieces |
P67105
|
FINISHED |
| Object | about 5000 artillery pieces and mortars |
—
|
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: about 5000 artillery pieces and mortars | Statement: [Battle of Königsberg, sovietArtilleryPieces, about 5000 artillery pieces and mortars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sovietArtilleryPieces Context triple: [Battle of Königsberg, sovietArtilleryPieces, about 5000 artillery pieces and mortars]
-
A.
SovietEquipmentLosses
Indicates the extent or instances of military equipment lost by Soviet forces in a given conflict or period.
-
B.
artilleryUsedBy
Indicates that a particular artillery asset is operated or employed by a specified user, such as a military unit, organization, or country.
-
C.
SovietDesignation
Indicates that an entity has been assigned an official designation or code name by Soviet authorities or according to Soviet classification systems.
-
D.
artilleryType
Indicates the specific category or kind of artillery associated with an entity or event.
-
E.
artilleryUsedIn
Indicates that a particular piece or type of artillery is employed or deployed in a specific event, operation, or context.
- 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_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. |
| PDg | Predicate description generation | batch_69c03fb6bb7c81909c5629fba408dc69 |
completed | March 22, 2026, 7:15 p.m. |
Created at: March 22, 2026, 4:03 p.m.