Triple
T34400381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (2029) |
E882961
|
entity |
| Predicate | hasPlannedEntryIntoServiceYear |
P193618
|
FINISHED |
| Object | 2029 |
—
|
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: 2029 | Statement: [SS Empress of Canada (2029), hasPlannedEntryIntoServiceYear, 2029]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedEntryIntoServiceYear Context triple: [SS Empress of Canada (2029), hasPlannedEntryIntoServiceYear, 2029]
-
A.
enteredFullServiceYear
Indicates the year in which an entity began operating at its full, regular level of service.
-
B.
hasFirstCohortYear
Indicates the year in which the first cohort associated with an entity began or was established.
-
C.
hasPlannedInstitution
Indicates that an entity has an associated institution that is intended or scheduled to be established or implemented in the future.
-
D.
hasPlanningPeriod
Indicates that an entity is associated with a defined time span allocated for planning activities.
-
E.
hasPlannedAccess
Indicates that an entity is expected or scheduled to have access to another entity or resource in the future, according to a plan or arrangement.
- 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_69f349c1304081909331872829e38106 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
| PDg | Predicate description generation | batch_69fd4d16dd20819096957c40f43cd971 |
completed | May 8, 2026, 2:40 a.m. |
Created at: May 1, 2026, 1:59 a.m.