Triple
T23951210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Portland (1653) |
E603049
|
entity |
| Predicate | EnglishSide |
P154470
|
FINISHED |
| Object | Commonwealth 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: Commonwealth Navy | Statement: [Battle of Portland (1653), EnglishSide, Commonwealth Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EnglishSide Context triple: [Battle of Portland (1653), EnglishSide, Commonwealth Navy]
-
A.
englishFlagship
Indicates that an entity participates in or is associated with an English flagship program (typically an intensive, advanced English language or studies track).
-
B.
englishNetwork
Indicates that there is a network-based relationship or connection specifically involving the English language between the related entities.
-
C.
EnglishTranslation
Indicates that one expression is the English-language translation equivalent of another expression.
-
D.
EnglishStrength
Indicates the degree or level of proficiency or capability in using the English language.
-
E.
EnglishCommander
Indicates that one entity serves as a military commander or leader for English forces in relation to another entity.
- 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.