Triple
T37530107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (1997) |
E933011
|
entity |
| Predicate | operatedUnderDifferentNames |
P81311
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [SS Empress of Canada (1997), operatedUnderDifferentNames, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedUnderDifferentNames Context triple: [SS Empress of Canada (1997), operatedUnderDifferentNames, yes]
-
A.
operatedAsNameUntil
Indicates that an entity functioned or was known under a particular name up to a specified point in time.
-
B.
laterOperatedUnder
chosen
Indicates that an entity, after an earlier period, was subsequently managed, controlled, or conducted under a different name, organization, framework, or operational context.
-
C.
historicalNameUsedIn
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
D.
heldAtFormerName
Indicates that an event or activity took place at a location when it was known by a previous or former name.
-
E.
underwentNameChangeTo
Indicates that an entity previously known by one name has changed its name to the specified new name.
- 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a0303622ce08190b359c9d247268729 |
completed | May 12, 2026, 10:39 a.m. |
| PD | Predicate disambiguation | batch_6a03030c02fc81908e546dba291b1240 |
completed | May 12, 2026, 10:38 a.m. |
Created at: May 3, 2026, 4:17 p.m.