Triple
T15244689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard With |
E364348
|
entity |
| Predicate | startTimeOfHurtigrutenService |
P117755
|
FINISHED |
| Object | 1893-07-02 |
—
|
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: 1893-07-02 | Statement: [Richard With, startTimeOfHurtigrutenService, 1893-07-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startTimeOfHurtigrutenService Context triple: [Richard With, startTimeOfHurtigrutenService, 1893-07-02]
-
A.
firstPassengerTrainDate
Indicates the calendar date on which the first passenger train service for the subject began operating.
-
B.
maidenVoyageStartDate
Indicates the calendar date on which something (typically a vessel or vehicle) undertakes its first official voyage or operational journey.
-
C.
busServiceOpeningDate
Indicates the date on which a particular bus service first began operating.
-
D.
touristServicesResumedYear
Indicates the year in which tourist services that were previously halted or disrupted began operating again.
-
E.
operatorStartDate
Indicates the date on which an operator’s role, activity, or responsibility begins.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f306f08190be448b215d6c9b6c |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:13 a.m.