Triple
T37523002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Queen Charlotte (1790) |
E932829
|
entity |
| Predicate | commanderAtGloriousFirstOfJune |
P195620
|
FINISHED |
| Object | Admiral Richard Howe, 1st Earl Howe |
—
|
NE NERFINISHED |
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: Admiral Richard Howe, 1st Earl Howe | Statement: [HMS Queen Charlotte (1790), commanderAtGloriousFirstOfJune, Admiral Richard Howe, 1st Earl Howe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commanderAtGloriousFirstOfJune Context triple: [HMS Queen Charlotte (1790), commanderAtGloriousFirstOfJune, Admiral Richard Howe, 1st Earl Howe]
-
A.
battleSecuredForNapoleon
Indicates that a battle was won or decisively secured in favor of Napoleon.
-
B.
battleDate(Barfleur)
Indicates the date on which the Battle of Barfleur took place.
-
C.
opponentInBattleOfCherbourg
Indicates that two entities were opposing sides against each other in the Battle of Cherbourg.
-
D.
navalCommanderAtBattleOfNavarino
Indicates that a person served as a naval commander participating in the Battle of Navarino.
-
E.
commanderAtBattleOfCoronel
Indicates that the subject served as a military commander during the Battle of Coronel.
- F. None of above. chosen
Provenance (4 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_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69fddac42c4081908568649058e86458 |
completed | May 8, 2026, 12:44 p.m. |
Created at: May 3, 2026, 4:17 p.m.