Triple
T33620116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Director |
E861240
|
entity |
| Predicate | afterEventCommander |
P180575
|
FINISHED |
| Object | William Bligh after the Bounty mutiny |
—
|
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: William Bligh after the Bounty mutiny | Statement: [HMS Director, afterEventCommander, William Bligh after the Bounty mutiny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterEventCommander Context triple: [HMS Director, afterEventCommander, William Bligh after the Bounty mutiny]
-
A.
eventCommanded
Indicates that one entity issued an order or directive for another entity to carry out a specific event or action.
-
B.
setAfterEventsOf
Indicates that one event or state is positioned or scheduled to occur after the completion of one or more specified preceding events.
-
C.
settingAfterEvent
Indicates that a particular setting or state occurs subsequent to, and as a result of or in temporal sequence with, a specified event.
-
D.
usedAfterEventFor
Indicates that one entity is used only after a specified event has occurred or been completed.
-
E.
changesAfterEvents
Indicates that one entity undergoes a change as a consequence of, or following, the occurrence of specified events.
- 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: May 1, 2026, 1:41 a.m.