Triple
T3870558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Great Britain |
E91974
|
entity |
| Predicate | retirementFromPassengerServiceYear |
P5918
|
FINISHED |
| Object | 1876 |
—
|
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: 1876 | Statement: [SS Great Britain, retirementFromPassengerServiceYear, 1876]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retirementFromPassengerServiceYear Context triple: [SS Great Britain, retirementFromPassengerServiceYear, 1876]
-
A.
retirementDate
Indicates the date on which an entity stops its active role or service, typically marking the end of its professional or operational period.
-
B.
retirementPeriod
Indicates the time span during which an entity is considered to be retired or in retirement status.
-
C.
retirementYear
chosen
Indicates the specific year in which an entity retires or is officially considered retired.
-
D.
retiredFrom
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
E.
activeYearsEndTime
Indicates the point in time when an entity’s period of activity or operation comes to an end.
- 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_69aed9645f348190a9868e7cef56ab7e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec54b0848190a8d4a0e4df7b6227 |
completed | March 9, 2026, 3:50 p.m. |
| PD | Predicate disambiguation | batch_69aee754dddc8190936e1f9c40a770db |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.