Triple
T22778831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cape Bon |
E563777
|
entity |
| Predicate | AlliedShipType |
P3141
|
FINISHED |
| Object | destroyer |
—
|
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: destroyer | Statement: [Battle of Cape Bon, AlliedShipType, destroyer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: AlliedShipType Context triple: [Battle of Cape Bon, AlliedShipType, destroyer]
-
A.
primaryAlliedCruiser
Indicates that one entity serves as the main or principal allied cruiser associated with another entity.
-
B.
shipClass
chosen
Indicates the classification or type category to which a particular ship belongs.
-
C.
commissionedShip
Indicates that a ship has been formally placed into active service, typically following its construction or acquisition.
-
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.
shipTypeProduced
Indicates that a particular type of ship is produced, built, or manufactured by a given entity.
- 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b631c6881908a6687920923dcf4 |
completed | April 29, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:28 p.m.