Triple
T24745124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Coast Limited |
E618673
|
entity |
| Predicate | hadService |
P80195
|
FINISHED |
| Object | sleeping cars |
—
|
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: sleeping cars | Statement: [North Coast Limited, hadService, sleeping cars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadService Context triple: [North Coast Limited, hadService, sleeping cars]
-
A.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
B.
hadCustom
Indicates that an entity previously possessed or was associated with a customized or user-defined version of something.
-
C.
hadOnboardService
chosen
Indicates that an onboard service was provided or available during a particular trip, journey, or transport event.
-
D.
hasHad
Indicates that an entity previously experienced, possessed, or was involved in something at some point in the past.
-
E.
hadOrgan
Indicates that an entity previously possessed or contained a specific organ as part of its body.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f410a25ab88190a72db43043c1f6ff |
completed | May 1, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f40ef612c88190ab2f3f08d4a92018 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 4:21 a.m.