Triple
T22522057
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Vågen |
E556804
|
entity |
| Predicate | approximateDutchShips |
P39920
|
FINISHED |
| Object | 10 East Indiamen |
—
|
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: 10 East Indiamen | Statement: [Battle of Vågen, approximateDutchShips, 10 East Indiamen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDutchShips Context triple: [Battle of Vågen, approximateDutchShips, 10 East Indiamen]
-
A.
BritishShipRate
Indicates that the subject is classified or rated according to the British naval ship rating system (e.g., first-rate, second-rate, etc.).
-
B.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
C.
shipsOfTheLine
Indicates a relationship where the associated entities are classified as ships of the line, i.e., major warships designed to participate in the main line of battle.
-
D.
numberOfShips
chosen
Indicates the quantity of ships associated with a given entity or situation.
-
E.
dispositionOfShips
Indicates the arrangement, allocation, or positioning of ships relative to a plan, location, or situation.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e32b8a88190ac335d4298dd5ee3 |
completed | April 29, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:50 p.m.