Triple
T32841478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Bounty mutineers |
E839983
|
entity |
| Predicate | setAdrift |
P42628
|
FINISHED |
| Object | William Bligh |
—
|
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: William Bligh | Statement: [HMS Bounty mutineers, setAdrift, William Bligh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setAdrift Context triple: [HMS Bounty mutineers, setAdrift, William Bligh]
-
A.
setAdriftWith
Indicates that one entity causes another to be left floating or drifting without control or guidance, typically in a body of water or space.
-
B.
isAbandonedAtSeaBy
chosen
Indicates that one entity is deliberately left behind or deserted at sea by another entity.
-
C.
strandedIn
Indicates that an entity is left isolated or stuck in a particular place or situation without the means to leave or resolve it.
-
D.
strandedAfter
Indicates that one entity is left isolated or unable to proceed as a consequence of another entity’s prior action or departure.
-
E.
strandedWith
Indicates that one entity is stuck or left without means to leave in the company or presence of another 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_69f3493ff0888190b51e974eae2a7834 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:16 a.m.