Triple
T27068868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Monarch |
E685256
|
entity |
| Predicate | gunneryRole |
P145654
|
FINISHED |
| Object | broadside engagements |
—
|
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: broadside engagements | Statement: [HMS Monarch, gunneryRole, broadside engagements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gunneryRole Context triple: [HMS Monarch, gunneryRole, broadside engagements]
-
A.
gunner
Indicates a person who operates, fires, or is responsible for a gun or artillery weapon in a combat or defense context.
-
B.
refersToArmamentRole
Indicates that one entity specifies or denotes the armament-related role or function associated with another entity.
-
C.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
D.
navalTacticRole
Indicates the specific tactical function or role an entity performs within a naval operation or maritime combat context.
-
E.
navalEngagementRole
chosen
Indicates the specific function or duty an entity performs within a naval engagement or maritime combat operation.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f622eb05c08190af8651dda80ace28 |
completed | May 2, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:26 a.m.