Triple
T34580659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (1966) |
E887888
|
entity |
| Predicate | enteredCarnivalServiceYear |
P182439
|
FINISHED |
| Object | 1972 |
—
|
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: 1972 | Statement: [SS Empress of Canada (1966), enteredCarnivalServiceYear, 1972]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredCarnivalServiceYear Context triple: [SS Empress of Canada (1966), enteredCarnivalServiceYear, 1972]
-
A.
enteredBRServiceYear
Indicates the year in which an entity began its service or operation within the BR (British Rail) system.
-
B.
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.
-
C.
ceremonyYear
Indicates the year in which a particular ceremony took place.
-
D.
joinedConferenceYear
Indicates the year in which an entity became a participant or member of a particular conference.
-
E.
enteredServiceOn
Indicates the date or time when an entity first began active use, operation, or service.
- 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_69f349d25cbc8190869998de5915886b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f78d7211a48190bfb59c406f0bf12f |
completed | May 3, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
| PDg | Predicate description generation | batch_69f78c6014e08190864785a4fe3e8e73 |
completed | May 3, 2026, 5:56 p.m. |
Created at: May 1, 2026, 2:03 a.m.