Triple
T28082416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bounty Islands |
E709718
|
entity |
| Predicate | discoveryVessel |
P110548
|
FINISHED |
| Object | HMS Bounty |
—
|
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 Bounty | Statement: [Bounty Islands, discoveryVessel, HMS Bounty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoveryVessel Context triple: [Bounty Islands, discoveryVessel, HMS Bounty]
-
A.
discoveryVoyage
Indicates a voyage undertaken with the primary purpose of exploring or discovering previously unknown or uncharted places, phenomena, or information.
-
B.
namedVesselOf
chosen
Indicates that one entity is the specific named vessel (e.g., ship, boat, or craft) associated with or belonging to another entity.
-
C.
discoveryExpedition
Indicates an expedition undertaken with the purpose of exploring or discovering new places, phenomena, or information.
-
D.
vesselLaunched
Indicates that a vessel has been formally set afloat or put into operation at a specific time or place.
-
E.
vesselDesignation
Indicates that a specific identifying designation (such as a name, number, or code) is assigned to a vessel.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 27, 2026, 8:53 p.m.