Triple
T30965782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Celeste |
E788952
|
entity |
| Predicate | finalVoyageDepartureDate |
P96319
|
FINISHED |
| Object | 7 November 1872 |
—
|
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: 7 November 1872 | Statement: [Mary Celeste, finalVoyageDepartureDate, 7 November 1872]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalVoyageDepartureDate Context triple: [Mary Celeste, finalVoyageDepartureDate, 7 November 1872]
-
A.
departureDateOnFinalVoyage
chosen
Indicates the date on which an entity began its final voyage or last recorded journey.
-
B.
dateOfDisembarkation
Indicates the specific date on which an individual or entity got off or was released from a vehicle, vessel, or mode of transport.
-
C.
maidenVoyageEndDate
Indicates the date on which something’s first official journey or operation was completed.
-
D.
departurePortOnFinalVoyage
Indicates the port from which an entity (such as a vessel) last departed on its final recorded voyage.
-
E.
destinationOnFinalVoyage
Indicates the place where an entity ultimately arrived or was intended to arrive on its final journey or last voyage.
- 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_69f224c3a6b48190951add9b7b7f0271 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: April 29, 2026, 8:54 p.m.