Triple
T36762514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (2037) |
E908242
|
entity |
| Predicate | hasPlannedEraOfOperation |
P28914
|
FINISHED |
| Object | 21st 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: 21st century | Statement: [SS Empress of Canada (2037), hasPlannedEraOfOperation, 21st century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedEraOfOperation Context triple: [SS Empress of Canada (2037), hasPlannedEraOfOperation, 21st century]
-
A.
hasPlanningPeriod
Indicates that an entity is associated with a defined time span allocated for planning activities.
-
B.
eraOfOperation
chosen
Indicates the time period or span of years during which an entity was active or in operation.
-
C.
managedEra
Indicates that one entity oversaw, directed, or was responsible for the management of a particular historical or temporal period associated with another entity.
-
D.
proposedEra
Indicates that one entity has suggested or put forward a particular era or time period as relevant or applicable to another entity or context.
-
E.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal 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_69f76e786ba481909cdcf6cf6b39dd32 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe163a41a0819098403b470e327d29 |
completed | May 8, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fe1358db5c819092570814a37ef5bd |
completed | May 8, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:12 p.m.