Triple
T1481136
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Camperdown |
E30957
|
entity |
| Predicate | DutchShipsOfTheLineEngaged |
P861
|
FINISHED |
| Object | approximately 16 |
—
|
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: approximately 16 | Statement: [Battle of Camperdown, DutchShipsOfTheLineEngaged, approximately 16]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DutchShipsOfTheLineEngaged Context triple: [Battle of Camperdown, DutchShipsOfTheLineEngaged, approximately 16]
-
A.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
B.
capturedShip
Indicates that one party has taken control of another party's ship, typically by force or seizure.
-
C.
navalForceInvolved
Indicates that a naval military force participates in, contributes to, or is otherwise involved in a specified event or operation.
-
D.
numberOfShipsInvolved
chosen
Indicates the total count of ships that participated or were involved in a specified event or situation.
-
E.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
- 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_69a498fe55a88190ab7f9e40ace88e49 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c67699848190852e376efe22737c |
completed | March 1, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69a4c484e52c81908948ff8c0a42751b |
completed | March 1, 2026, 10:58 p.m. |
Created at: March 1, 2026, 8:11 p.m.