Triple
T14066794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Ramillies |
E338494
|
entity |
| Predicate | gundeckArmamentRole |
P84541
|
FINISHED |
| Object | line-of-battle ship |
—
|
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: line-of-battle ship | Statement: [HMS Ramillies, gundeckArmamentRole, line-of-battle ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gundeckArmamentRole Context triple: [HMS Ramillies, gundeckArmamentRole, line-of-battle ship]
-
A.
refersToArmamentRole
chosen
Indicates that one entity specifies or denotes the armament-related role or function associated with another entity.
-
B.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
C.
primaryArmamentLayout
Indicates how the main weapons or primary armament of an entity are arranged or distributed relative to that entity.
-
D.
weaponMount
Indicates that one entity serves as a mounting point or support structure for attaching or holding a weapon on another entity.
-
E.
armamentCapacity
Indicates the maximum quantity or type of weapons or munitions that something is designed or allowed to carry.
- 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_69d81c67ba6c819091935650dfb3b895 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de568b81f08190a571004261c0e8e4 |
completed | April 14, 2026, 3 p.m. |
| PD | Predicate disambiguation | batch_69de05adef888190b023ab42ef5076b6 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:21 p.m.