Triple
T29847780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Kentish Knock |
E757975
|
entity |
| Predicate | dutchAdmiraltiesInvolved |
P23973
|
FINISHED |
| Object | Admiralty of Amsterdam |
—
|
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: Admiralty of Amsterdam | Statement: [Battle of the Kentish Knock, dutchAdmiraltiesInvolved, Admiralty of Amsterdam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dutchAdmiraltiesInvolved Context triple: [Battle of the Kentish Knock, dutchAdmiraltiesInvolved, Admiralty of Amsterdam]
-
A.
DutchFleetStrength
Indicates the relative size or power of the Dutch fleet in a given context or time period.
-
B.
navalForceInvolved
chosen
Indicates that a naval military force participates in, contributes to, or is otherwise involved in a specified event or operation.
-
C.
dutchShipsOfTheLine
Indicates that the subject is a Dutch ship of the line, i.e., a large warship belonging to the Dutch navy designed to fight in the line of battle.
-
D.
DutchCommander
Indicates that an entity serves as a military commander associated with the Netherlands.
-
E.
navalCampaignParticipation
Indicates involvement of an entity in a specific naval campaign as a participant or contributor.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6764489c881909618ff635fe6c410 |
completed | May 2, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 5:42 p.m.