Triple
T33106378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christopher Cradock |
E847199
|
entity |
| Predicate | shipLostUnderCommand |
P94181
|
FINISHED |
| Object | HMS Good Hope |
—
|
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: HMS Good Hope | Statement: [Christopher Cradock, shipLostUnderCommand, HMS Good Hope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shipLostUnderCommand Context triple: [Christopher Cradock, shipLostUnderCommand, HMS Good Hope]
-
A.
lostToSea
Indicates that something has been carried away or disappeared into the sea, resulting in its loss.
-
B.
hullLoss
Indicates that an aircraft has suffered damage or destruction severe enough to be considered a total loss of the airframe.
-
C.
sankWhile
Indicates that one entity moved downward below a surface or level at the same time that another specified event or action was occurring.
-
D.
shipSankIn
Indicates that a specific ship sank (was lost or submerged) in a particular location or body of water.
-
E.
shipwreck
chosen
Indicates that a vessel has been destroyed, stranded, or severely damaged, typically at sea or near a shoreline.
- 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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6e7c0248190a5eed4c5bcf83aad |
completed | May 3, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:26 a.m.