Triple
T6720109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Night Riviera sleeper service |
E153371
|
entity |
| Predicate | arrivalTimePattern |
P72869
|
FINISHED |
| Object | early morning arrival in Cornwall |
—
|
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: early morning arrival in Cornwall | Statement: [Night Riviera sleeper service, arrivalTimePattern, early morning arrival in Cornwall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arrivalTimePattern Context triple: [Night Riviera sleeper service, arrivalTimePattern, early morning arrival in Cornwall]
-
A.
arrivalAt
Indicates the event or state of an entity reaching and being present at a specific destination or location.
-
B.
departureTime
Indicates the specific time at which an entity leaves or begins its departure from a location or state.
-
C.
attendsTo
Indicates that one entity directs care, attention, or service toward another entity or task.
-
D.
rushHourServicePattern
Indicates that a service operates according to a specific pattern or schedule that applies only during rush-hour or peak travel times.
-
E.
checkInTime
Indicates the time at which an entity arrives at and formally registers its presence at a specified place or event.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d137084881908e04ee6b2bd45585 |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d11fab808190b18160ff3829fcc6 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:07 p.m.