Triple
T11823599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Great Western |
E281200
|
entity |
| Predicate | maidenVoyageEndDate |
P101691
|
FINISHED |
| Object | 1838-04-23 |
—
|
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: 1838-04-23 | Statement: [SS Great Western, maidenVoyageEndDate, 1838-04-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maidenVoyageEndDate Context triple: [SS Great Western, maidenVoyageEndDate, 1838-04-23]
-
A.
maidenVoyageStartDate
Indicates the calendar date on which something (typically a vessel or vehicle) undertakes its first official voyage or operational journey.
-
B.
firstVoyageEndYear
Indicates the calendar year in which an entity’s first voyage or initial journey was completed or came to an end.
-
C.
voyageStartYearDescribed
Indicates the year in which a voyage is described as having started.
-
D.
voyageYear
Indicates the calendar year in which a particular voyage or journey took place.
-
E.
expeditionEndYear
Indicates the calendar year in which an expedition or journey was completed or officially ended.
- F. None of above. chosen
Provenance (4 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5e9c50481909b2287a0b23d2094 |
completed | April 10, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69d8a251fc08819095933f1d13c3b742 |
completed | April 10, 2026, 7:10 a.m. |
| PDg | Predicate description generation | batch_69d8a43cc0c881909fed7cd759fe90b1 |
completed | April 10, 2026, 7:18 a.m. |
Created at: April 8, 2026, 9:42 p.m.