Triple
T34342792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Britain (2009) |
E881338
|
entity |
| Predicate | hasLaterRole |
P199270
|
FINISHED |
| Object | cruise ship |
—
|
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: cruise ship | Statement: [SS Empress of Britain (2009), hasLaterRole, cruise ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLaterRole Context triple: [SS Empress of Britain (2009), hasLaterRole, cruise ship]
-
A.
hasAuthorLaterRole
Indicates that an author of a work later took on an additional or subsequent role related to that work or its context.
-
B.
hasLaterMember
Indicates that one member in an ordered sequence occurs later than another member in that same sequence.
-
C.
subsequentRole
Indicates that one role or position is held after, and in succession to, another role or position.
-
D.
hasEarlyRoleFor
Indicates that one entity holds or performs an initial or early-stage role in relation to another entity or process.
-
E.
successorInSomeRoles
Indicates that one entity has taken over or followed another entity in certain specified roles or positions.
- F. None of above. chosen
Provenance (4 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff29d831b881908d485609e0fc1d0b |
completed | May 9, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_69ff28f9f9e4819087f3402735de66c7 |
completed | May 9, 2026, 12:30 p.m. |
| PDg | Predicate description generation | batch_69ff29d77f48819085304ed5e92eb906 |
completed | May 9, 2026, 12:34 p.m. |
Created at: May 1, 2026, 1:58 a.m.