Triple
T13278546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Vega |
E316255
|
entity |
| Predicate | departureYearOfNortheastPassageVoyage |
P7984
|
FINISHED |
| Object | 1878 |
—
|
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: 1878 | Statement: [SS Vega, departureYearOfNortheastPassageVoyage, 1878]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: departureYearOfNortheastPassageVoyage Context triple: [SS Vega, departureYearOfNortheastPassageVoyage, 1878]
-
A.
departureYear
chosen
Indicates the calendar year in which an entity leaves, exits, or ceases its association with another entity or location.
-
B.
departureDateOnFinalVoyage
Indicates the date on which an entity began its final voyage or last recorded journey.
-
C.
dateOfExpedition
Indicates the specific calendar date on which an expedition or journey was initiated or carried out.
-
D.
annualDepartureDate
Indicates the calendar date each year on which a recurring departure regularly takes place.
-
E.
voyageStartYearDescribed
Indicates the year in which a voyage is described as having started.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.