Triple
T34216900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blohm & Voss BV 138 |
E877816
|
entity |
| Predicate | armamentPosition |
P99830
|
FINISHED |
| Object | bow turret |
—
|
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: bow turret | Statement: [Blohm & Voss BV 138, armamentPosition, bow turret]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armamentPosition Context triple: [Blohm & Voss BV 138, armamentPosition, bow turret]
-
A.
armamentConfiguration
Indicates how weapons or armaments are arranged, equipped, or configured on an entity in a given context.
-
B.
positionOnWeapons
Indicates a stance, policy, or viewpoint that an entity holds regarding weapons or weapon-related issues.
-
C.
primaryArmamentLayout
chosen
Indicates how the main weapons or primary armament of an entity are arranged or distributed relative to that entity.
-
D.
armamentIncludes
Indicates that a larger weapon system, vehicle, or platform has a specified weapon or piece of equipment as part of its armament.
-
E.
armamentNote
Indicates a note or comment providing additional information or clarification about an armament or weapon-related detail.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7107e66e88190a799e0c78f1af117 |
completed | May 3, 2026, 9:08 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.