Triple
T14402938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HMS Bounty |
E357114
|
entity |
| Predicate | voyageDepartureDate |
P24300
|
FINISHED |
| Object | 23 December 1787 |
—
|
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: 23 December 1787 | Statement: [HMS Bounty, voyageDepartureDate, 23 December 1787]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voyageDepartureDate Context triple: [HMS Bounty, voyageDepartureDate, 23 December 1787]
-
A.
expeditionDepartureDate
chosen
Indicates the date on which an expedition is scheduled to or actually does depart.
-
B.
departureDateOnFinalVoyage
Indicates the date on which an entity began its final voyage or last recorded journey.
-
C.
dateOfJourney
Indicates the specific calendar date on which a particular journey or trip takes place.
-
D.
departureYear
Indicates the calendar year in which an entity leaves, exits, or ceases its association with another entity or location.
-
E.
dateOfDisembarkation
Indicates the specific date on which an individual or entity got off or was released from a vehicle, vessel, or mode of transport.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90860ae481908e175decda8624d5 |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:17 a.m.