Triple
T31588794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayflower passengers |
E806032
|
entity |
| Predicate | voyageEndDate |
P115917
|
FINISHED |
| Object | November 1620 |
—
|
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: November 1620 | Statement: [Mayflower passengers, voyageEndDate, November 1620]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: voyageEndDate Context triple: [Mayflower passengers, voyageEndDate, November 1620]
-
A.
departureDateOnFinalVoyage
Indicates the date on which an entity began its final voyage or last recorded journey.
-
B.
maidenVoyageEndDate
Indicates the date on which something’s first official journey or operation was completed.
-
C.
dateOfDisembarkation
Indicates the specific date on which an individual or entity got off or was released from a vehicle, vessel, or mode of transport.
-
D.
explorationEndDate
Indicates the date on which an exploration activity or process is completed or officially ends.
-
E.
timeOfJourneyEnd
chosen
Indicates the point in time at which a journey or trip concludes.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a80ef3988190bb192a8e483d1694 |
completed | May 3, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:27 p.m.