Triple
T36394469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Canada (2033) |
E896429
|
entity |
| Predicate | expectedEraOfService |
P48887
|
FINISHED |
| Object | 2030s |
—
|
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: 2030s | Statement: [SS Empress of Canada (2033), expectedEraOfService, 2030s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expectedEraOfService Context triple: [SS Empress of Canada (2033), expectedEraOfService, 2030s]
-
A.
hasTimePeriodOfService
Indicates that an entity is associated with a specific span of time during which it provided service or was actively serving.
-
B.
serviceEra
chosen
Indicates the historical period or era during which a service, role, or duty was performed.
-
C.
serviceNumberOrYearsOfService
Indicates a relationship that specifies either an entity’s service identification number or the duration of time the entity has served.
-
D.
eligibilityPeriod
Indicates the span of time during which an entity qualifies for or is allowed to receive a particular benefit, service, or status.
-
E.
typicalTimeInServiceToAttain
Indicates the usual duration of service required for an entity to reach or attain a specified status, level, or condition.
- 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_69f76e52e3108190becf70b090ae7bd6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:10 p.m.