Triple
T23951202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Portland (1653) |
E603049
|
entity |
| Predicate | DutchFleetCommanderRank |
P44838
|
FINISHED |
| Object | Lieutenant-Admiral |
—
|
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: Lieutenant-Admiral | Statement: [Battle of Portland (1653), DutchFleetCommanderRank, Lieutenant-Admiral]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DutchFleetCommanderRank Context triple: [Battle of Portland (1653), DutchFleetCommanderRank, Lieutenant-Admiral]
-
A.
navalRankContext
chosen
Indicates the relationship between an entity and its naval rank within a specific organizational, temporal, or situational context.
-
B.
commandingOfficerRank
Indicates the military rank held by the officer who has command authority over a given individual or unit.
-
C.
equivalentRankInPortugueseNavy
Indicates that two military ranks are considered equivalent in status or hierarchy within the Portuguese Navy.
-
D.
militaryRank
Indicates that one entity holds a specific position or level within a hierarchical military ranking system relative to another entity.
-
E.
airCommanderRank
Indicates that one entity holds the rank or position of air commander relative to another entity (such as a force, unit, 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_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. |
Created at: April 17, 2026, 9:20 p.m.