Triple
T2773565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cape St Vincent |
E61514
|
entity |
| Predicate | JervisTitle |
P39450
|
FINISHED |
| Object | later Earl St Vincent |
—
|
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: later Earl St Vincent | Statement: [Battle of Cape St Vincent, JervisTitle, later Earl St Vincent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JervisTitle Context triple: [Battle of Cape St Vincent, JervisTitle, later Earl St Vincent]
-
A.
representativeOfMonarchTitle
Indicates that one entity serves as the official representative or holder of authority on behalf of a monarch’s title.
-
B.
commanderTitle
Indicates the official rank or title held by the person who commands or leads a given entity.
-
C.
laterTitleOfCommander
chosen
Indicates that one title represents a later-held command position of the same commander who previously held another title.
-
D.
firstLordOfTheAdmiralty
Indicates that an entity holds or has held the position of First Lord of the Admiralty in relation to a governing body or navy.
-
E.
honoursTitle
Indicates that an entity holds or is designated by a formal honorific or honorary title.
- 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_69ab4b7cd13481909174bca9809ed259 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abddceb9d88190961e30d521a21552 |
completed | March 7, 2026, 8:11 a.m. |
| PD | Predicate disambiguation | batch_69abdcfed608819080988e93df7bdf7c |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 9:57 p.m.