Triple
T24704364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Dungeness (1652) |
E611845
|
entity |
| Predicate | notableShipEnglish |
P3345
|
FINISHED |
| Object | Triumph |
—
|
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: Triumph | Statement: [Battle of Dungeness (1652), notableShipEnglish, Triumph]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableShipEnglish Context triple: [Battle of Dungeness (1652), notableShipEnglish, Triumph]
-
A.
notableShip
chosen
Indicates that there is a notable or significant ship associated with the subject entity.
-
B.
approximateEnglishShips
Indicates that one entity is an estimated or approximate count of English ships associated with another entity or context.
-
C.
BritishShipType
Indicates that the entity is classified as a type of ship associated with Britain, typically by origin, design, or service.
-
D.
BritishShipRate
Indicates that the subject is classified or rated according to the British naval ship rating system (e.g., first-rate, second-rate, etc.).
-
E.
notableShipOnRoute
Indicates that a particular ship is especially significant or prominent among those operating on a given route.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f657f653448190a945b4751af8507d |
completed | May 2, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69f6575ba12081909396036f78757a76 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 18, 2026, 3:23 a.m.