Triple
T23951203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Portland (1653) |
E603049
|
entity |
| Predicate | EnglishFleetType |
P6198
|
FINISHED |
| Object | warships of the Commonwealth navy |
—
|
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: warships of the Commonwealth navy | Statement: [Battle of Portland (1653), EnglishFleetType, warships of the Commonwealth navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EnglishFleetType Context triple: [Battle of Portland (1653), EnglishFleetType, warships of the Commonwealth navy]
-
A.
EnglishFleetBase
Indicates a base or primary location associated with the English fleet in a given context.
-
B.
fleetCommander (British)
Indicates that the subject serves as the fleet commander for the British naval forces.
-
C.
fleetType
chosen
Indicates the category or classification of a fleet to which an entity belongs or with which it is associated.
-
D.
englishHullClassification
Indicates the English-language hull classification assigned to a vessel, specifying its type or role within a naval or maritime fleet.
-
E.
fleetName
Indicates the name assigned to a particular fleet within a system or context.
- 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_69e2953e4924819093f1c24c03476b42 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d03204348190a82876778d9cdd63 |
completed | April 29, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69f1615518088190a206f54e2fdb14a3 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:20 p.m.