Triple
T2849111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Orion |
E63049
|
entity |
| Predicate | roleAtBattleOfTrafalgar |
P39666
|
FINISHED |
| Object | engaged enemy ships in the lee column |
—
|
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: engaged enemy ships in the lee column | Statement: [HMS Orion, roleAtBattleOfTrafalgar, engaged enemy ships in the lee column]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleAtBattleOfTrafalgar Context triple: [HMS Orion, roleAtBattleOfTrafalgar, engaged enemy ships in the lee column]
-
A.
commandingOfficerBritishSide
Indicates that one entity serves as the commanding officer of another entity on the British side in a military context.
-
B.
notableNavalCommander
Indicates that the subject is recognized as a distinguished or historically significant commander in naval forces.
-
C.
navalTacticRole
chosen
Indicates the specific tactical function or role an entity performs within a naval operation or maritime combat context.
-
D.
roleAtBattleOfMidway
Indicates the specific role, position, or function an entity held or performed during the Battle of Midway.
-
E.
opponentInBattleOfTheRiverPlate
Indicates that two entities were opposing sides facing each other in the Battle of the River Plate.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf41ac24819087c5b72e3b84117c |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.