Triple
T36762433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Sussex |
E908239
|
entity |
| Predicate | cargoPurpose |
P186271
|
FINISHED |
| Object | to finance English allies in the Nine Years' War |
—
|
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: to finance English allies in the Nine Years' War | Statement: [HMS Sussex, cargoPurpose, to finance English allies in the Nine Years' War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cargoPurpose Context triple: [HMS Sussex, cargoPurpose, to finance English allies in the Nine Years' War]
-
A.
cargoDescription
Indicates that one entity provides a textual description or details about the cargo associated with another entity.
-
B.
orderPurpose
Indicates that an order is placed with the specific purpose or intended use of the ordered item or service.
-
C.
cargoForm
Indicates that one entity serves as the physical or structural form in which another entity’s cargo or contents are contained or transported.
-
D.
cargo
Indicates that one entity is the goods or load being transported, carried, or shipped by another entity.
-
E.
cargoContents
Indicates that one entity contains or carries another entity as its cargo.
- 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabacc1481909e839454ce1057f7 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7c9f4c7c48190ba918d8d5dc8dfd9 |
completed | May 3, 2026, 10:19 p.m. |
Created at: May 3, 2026, 4:12 p.m.