Triple
T38575938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Euryalus |
E929400
|
entity |
| Predicate | navalGunArmament |
P115826
|
FINISHED |
| Object | 5.25-inch dual-purpose guns |
—
|
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: 5.25-inch dual-purpose guns | Statement: [HMS Euryalus, navalGunArmament, 5.25-inch dual-purpose guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalGunArmament Context triple: [HMS Euryalus, navalGunArmament, 5.25-inch dual-purpose guns]
-
A.
navalArmament
Indicates that one entity serves as the naval weaponry or sea-based military equipment of another entity.
-
B.
gunDeckArmament
chosen
Indicates the type or configuration of weapons mounted on a ship’s gun deck.
-
C.
armamentAsBuilt
Indicates the weaponry or armament configuration that an object (such as a vehicle, vessel, or structure) originally had when it was first constructed or completed.
-
D.
navalTechnologyType
Indicates the specific category or type of naval technology associated with an entity.
-
E.
plannedArmament
Indicates that an entity has a specific weapon or set of weapons intended or scheduled to be equipped or deployed in the future.
- 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_69f76ebd2248819083978362d81fa35e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.