Triple
T22778846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Cape Bon |
E563777
|
entity |
| Predicate | ItalianCargo |
P5941
|
FINISHED |
| Object | aviation fuel |
—
|
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: aviation fuel | Statement: [Battle of Cape Bon, ItalianCargo, aviation fuel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ItalianCargo Context triple: [Battle of Cape Bon, ItalianCargo, aviation fuel]
-
A.
alignedItalyWith
Indicates that one entity brought Italy into political, military, or ideological agreement or cooperation with another entity.
-
B.
servesAsCargoHubFor
Indicates that one entity functions as a central location or facility for handling, consolidating, and distributing cargo associated with another entity.
-
C.
ItalianObjective
Indicates that an entity has an objective, goal, or target specifically related to Italy or the Italian context.
-
D.
mainCargo
chosen
Indicates that one entity serves as the primary or principal cargo carried or transported by another entity.
-
E.
ItalianVersionClaimed
Indicates that an entity asserts or is reported to have an Italian-language version.
- 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.