Triple
T37849344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (2003) |
E943996
|
entity |
| Predicate | hasServiceEntryYear |
P187429
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [SS Empress of Canada (2003), hasServiceEntryYear, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceEntryYear Context triple: [SS Empress of Canada (2003), hasServiceEntryYear, 2003]
-
A.
hasPlannedEntryIntoServiceYear
Indicates the year in which an entity is scheduled or planned to begin being in service or operational use.
-
B.
enteredFullServiceYear
chosen
Indicates the year in which an entity began operating at its full, regular level of service.
-
C.
enteredBRServiceYear
Indicates the year in which an entity began its service or operation within the BR (British Rail) system.
-
D.
hasTimePeriodOfService
Indicates that an entity is associated with a specific span of time during which it provided service or was actively serving.
-
E.
enteredServiceApproximateYear
Indicates that an entity began its service or operation around a specified year, where the year is an approximate rather than an exact value.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00acf86e4081909aad9356650e0f79 |
completed | May 10, 2026, 4:06 p.m. |
| PD | Predicate disambiguation | batch_6a00ac813fd08190a0a7782609e74e70 |
completed | May 10, 2026, 4:04 p.m. |
Created at: May 3, 2026, 4:19 p.m.