Triple
T37522973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Royal Sovereign (1786) |
E932828
|
entity |
| Predicate | navalTacticAtTrafalgar |
P45997
|
FINISHED |
| Object | broke the enemy line |
—
|
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: broke the enemy line | Statement: [HMS Royal Sovereign (1786), navalTacticAtTrafalgar, broke the enemy line]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: navalTacticAtTrafalgar Context triple: [HMS Royal Sovereign (1786), navalTacticAtTrafalgar, broke the enemy line]
-
A.
opponentAtTrafalgar
Indicates that one entity was an opposing side or adversary of the other in the Battle of Trafalgar.
-
B.
navalTacticRole
Indicates the specific tactical function or role an entity performs within a naval operation or maritime combat context.
-
C.
navalTacticsImpact
Indicates how naval tactics influence the outcome, effectiveness, or dynamics of a maritime operation or engagement.
-
D.
navalOpposition
Indicates a relationship where one party actively resists, confronts, or acts against another using naval or maritime military forces.
-
E.
roleAtTrafalgar
chosen
Indicates the specific role, position, or function an entity held during the Battle of Trafalgar.
- 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.