Triple
T37522956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Royal Sovereign (1786) |
E932828
|
entity |
| Predicate | enemyFleetAtTrafalgar |
P67151
|
FINISHED |
| Object | Combined Franco-Spanish fleet |
—
|
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: Combined Franco-Spanish fleet | Statement: [HMS Royal Sovereign (1786), enemyFleetAtTrafalgar, Combined Franco-Spanish fleet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enemyFleetAtTrafalgar Context triple: [HMS Royal Sovereign (1786), enemyFleetAtTrafalgar, Combined Franco-Spanish fleet]
-
A.
opponentAtTrafalgar
chosen
Indicates that one entity was an opposing side or adversary of the other in the Battle of Trafalgar.
-
B.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
-
C.
battleDate(Barfleur)
Indicates the date on which the Battle of Barfleur took place.
-
D.
shipsOfTheLine
Indicates a relationship where the associated entities are classified as ships of the line, i.e., major warships designed to participate in the main line of battle.
-
E.
SpanishFleetStrength
Indicates the relative size or power of a Spanish naval fleet in a given context or time.
- 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_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.