Triple
T29847831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Sound (1658) |
E757976
|
entity |
| Predicate | involvedWarshipsFrom |
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 Sound (1658), involvedWarshipsFrom, Admiralty of Amsterdam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvedWarshipsFrom Context triple: [Battle of the Sound (1658), involvedWarshipsFrom, Admiralty of Amsterdam]
-
A.
battleshipInvolved
Indicates that a battleship participates as an active party in a specific event, operation, or engagement.
-
B.
navalForceInvolved
chosen
Indicates that a naval military force participates in, contributes to, or is otherwise involved in a specified event or operation.
-
C.
numberOfShipsInvolved
Indicates the total count of ships that participated or were involved in a specified event or situation.
-
D.
AlliedShipsInvolved
Indicates that allied ships participated in or were involved in the specified event or operation.
-
E.
warshipTypeUsed
Indicates that a particular type or class of warship is employed or utilized in a given context, event, or operation.
- 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_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 29, 2026, 5:42 p.m.