Triple
T2585170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Minorca (1756) |
E57181
|
entity |
| Predicate | BritishShipsOfTheLine |
P40525
|
FINISHED |
| Object | 13 |
—
|
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: 13 | Statement: [Battle of Minorca (1756), BritishShipsOfTheLine, 13]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BritishShipsOfTheLine Context triple: [Battle of Minorca (1756), BritishShipsOfTheLine, 13]
-
A.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
-
B.
fleetStrengthEnglish
Indicates the relative military or naval power level associated with a fleet, expressed or categorized in English terms.
-
C.
fleetFlagshipOf
Indicates that one entity serves as the primary or leading flagship of a particular fleet.
-
D.
navalVesselsAlliedApprox
Indicates that two or more naval vessels are approximately allied, suggesting a cooperative or friendly relationship without specifying a precise or formal alliance.
-
E.
navalFleet
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3cd07588190b3cb8cc348f12938 |
completed | March 7, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69abd0d19308819089ee942513d567a4 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd37ef248819090ab6b86b67e355f |
completed | March 7, 2026, 7:27 a.m. |
Created at: March 6, 2026, 9:49 p.m.