Triple
T32841497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Bounty mutineers |
E839983
|
entity |
| Predicate | someMembersStayedOn |
P99579
|
FINISHED |
| Object | Tahiti |
—
|
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: Tahiti | Statement: [HMS Bounty mutineers, someMembersStayedOn, Tahiti]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: someMembersStayedOn Context triple: [HMS Bounty mutineers, someMembersStayedOn, Tahiti]
-
A.
remainedIn
chosen
Indicates that an entity stayed within or continued to be located in a particular place or state for a period of time.
-
B.
someMembersLater
Indicates that at least some members of a group or set occur, appear, or hold a property at a later time relative to another reference point or group.
-
C.
staysWith
Indicates that one entity remains in the company or presence of another entity for a period of time.
-
D.
someFormerMembersNowIn
Indicates that certain entities that were previously members of one group or organization are now members of another specified group or organization.
-
E.
someMembersExhibit
Indicates that within a group or collection, at least one member displays or possesses a specified property, behavior, or characteristic.
- 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.