Triple
T9388915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vickers 14-inch naval gun |
E225972
|
entity |
| Predicate | firingPlatformType |
P74643
|
FINISHED |
| Object | turret-mounted gun |
—
|
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: turret-mounted gun | Statement: [Vickers 14-inch naval gun, firingPlatformType, turret-mounted gun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firingPlatformType Context triple: [Vickers 14-inch naval gun, firingPlatformType, turret-mounted gun]
-
A.
firingPlatform
chosen
Indicates a platform or structure from which a weapon or projectile is launched or fired.
-
B.
fireSupportType
Indicates the specific kind or category of supporting fire (such as artillery, air support, or naval gunfire) being provided in a military context.
-
C.
catapultType
Indicates the specific kind or category of catapult associated with an entity or event.
-
D.
firingControl
Indicates a relationship where one entity directs, regulates, or initiates the firing or discharge action of another entity or system.
-
E.
firingCharacteristic
Indicates the specific way in which an entity initiates or sustains firing or discharge, such as its pattern, mode, or conditions of activation.
- 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_69ca842e9dcc8190a264119e683cfe04 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd50d6e5f081908102909cb4cbb649 |
completed | April 1, 2026, 5:07 p.m. |
| PD | Predicate disambiguation | batch_69cca53bd6ec81909bf403ce304e5c08 |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:45 p.m.