Triple
T26546723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Macedonian |
E671552
|
entity |
| Predicate | armamentDetail |
P137518
|
FINISHED |
| Object | additional carronades |
—
|
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: additional carronades | Statement: [HMS Macedonian, armamentDetail, additional carronades]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armamentDetail Context triple: [HMS Macedonian, armamentDetail, additional carronades]
-
A.
armamentIncludes
Indicates that a larger weapon system, vehicle, or platform has a specified weapon or piece of equipment as part of its armament.
-
B.
armamentNote
chosen
Indicates a note or comment providing additional information or clarification about an armament or weapon-related detail.
-
C.
armamentCategory
Indicates the classification of a weapon or military equipment according to its type or role in armament systems.
-
D.
armamentCount
Indicates the number of weapons or armaments associated with an entity.
-
E.
armamentConfiguration
Indicates how weapons or armaments are arranged, equipped, or configured on an entity in a given context.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61436eee08190a23739d9347ec088 |
completed | May 2, 2026, 3:11 p.m. |
| PD | Predicate disambiguation | batch_69f60b89cc048190a9feb24466006be0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 1:44 a.m.