Triple
T36938981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (1984) |
E913697
|
entity |
| Predicate | hasServiceEra |
P48887
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [SS Empress of Canada (1984), hasServiceEra, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasServiceEra Context triple: [SS Empress of Canada (1984), hasServiceEra, late 20th century]
-
A.
hasLaunchEra
Indicates the time period or era during which an entity (such as a product, mission, or project) was initially launched or introduced.
-
B.
serviceEra
chosen
Indicates the historical period or era during which a service, role, or duty was performed.
-
C.
hasTimePeriodOfService
Indicates that an entity is associated with a specific span of time during which it provided service or was actively serving.
-
D.
refersToEraOfCareer
Indicates that one entity specifies or denotes the particular era or phase within another entity’s career.
-
E.
playedWithEra
Indicates that an entity performed or was active during a specified historical or stylistic era.
- 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_6a006ef900148190ba52daf566882a03 |
completed | May 10, 2026, 11:41 a.m. |
| PD | Predicate disambiguation | batch_6a006c76ae748190bfe466d7d17d321e |
completed | May 10, 2026, 11:31 a.m. |
Created at: May 3, 2026, 4:13 p.m.