Triple
T23951211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Portland (1653) |
E603049
|
entity |
| Predicate | DutchSide |
P154471
|
FINISHED |
| Object | Dutch Navy |
—
|
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: Dutch Navy | Statement: [Battle of Portland (1653), DutchSide, Dutch Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DutchSide Context triple: [Battle of Portland (1653), DutchSide, Dutch Navy]
-
A.
DutchCommander
Indicates that an entity serves as a military commander associated with the Netherlands.
-
B.
harbourSide
Indicates a location or object that is situated alongside or directly adjacent to a harbour.
-
C.
FrenchSide
Indicates that an entity is positioned on, associated with, or belongs to the French side of a border, division, or relationship.
-
D.
Sneekweek
Indicates participation in or association with the Dutch student sailing and water sports event known as Sneekweek.
-
E.
Waterline
Indicates the level or line on an object or surface that marks where water reaches or has reached.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 9:20 p.m.