Triple
T36938966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (1984) |
E913697
|
entity |
| Predicate | carriesHistoricName |
P66486
|
FINISHED |
| Object | Empress of Canada |
—
|
NE NERFINISHED |
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: Empress of Canada | Statement: [SS Empress of Canada (1984), carriesHistoricName, Empress of Canada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriesHistoricName Context triple: [SS Empress of Canada (1984), carriesHistoricName, Empress of Canada]
-
A.
isHistoricalName
Indicates that a given name is a former or past designation historically used for an entity.
-
B.
historicalNameUsedIn
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
C.
historicalNameType
Indicates that the relationship specifies the type or category of a historical name associated with an entity.
-
D.
hasHistoricNameVariant
chosen
Indicates that an entity has an alternative name that was used in a historical period or past context.
-
E.
regionHistoricalName
Indicates that a region has been known by a particular historical name during some past period.
- 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:13 p.m.