Triple
T30965781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Celeste |
E788952
|
entity |
| Predicate | finalVoyageDeparturePort |
P96318
|
FINISHED |
| Object | New York City |
—
|
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: New York City | Statement: [Mary Celeste, finalVoyageDeparturePort, New York City]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalVoyageDeparturePort Context triple: [Mary Celeste, finalVoyageDeparturePort, New York City]
-
A.
departurePortOnFinalVoyage
chosen
Indicates the port from which an entity (such as a vessel) last departed on its final recorded voyage.
-
B.
destinationOnFinalVoyage
Indicates the place where an entity ultimately arrived or was intended to arrive on its final journey or last voyage.
-
C.
destinationOfVoyageTo
Indicates the endpoint location that a particular voyage or journey is directed toward or arrives at.
-
D.
placeOfDeparture
Indicates the location from which an entity, such as a person or vehicle, begins its journey or movement.
-
E.
departureDateOnFinalVoyage
Indicates the date on which an entity began its final voyage or last recorded journey.
- 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_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 29, 2026, 8:54 p.m.