Triple
T34342791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Britain (2009) |
E881338
|
entity |
| Predicate | hasOriginalRole |
P197371
|
FINISHED |
| Object | ocean liner |
—
|
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: ocean liner | Statement: [SS Empress of Britain (2009), hasOriginalRole, ocean liner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOriginalRole Context triple: [SS Empress of Britain (2009), hasOriginalRole, ocean liner]
-
A.
hasOriginalCharacter
Indicates that an entity includes, features, or is associated with an original character distinct from pre-existing or canonical characters.
-
B.
hasOriginalVersion
Indicates that one entity is the original or initial version from which another entity is derived or adapted.
-
C.
hasOriginalFeature
Indicates that an entity possesses a feature or characteristic in its initial, unmodified, or native form.
-
D.
hasOriginalCharacterOwner
Indicates that an entity is the original owner or creator of a given character.
-
E.
hasOriginalPart
Indicates that an entity includes a component or segment that is part of its initial, original composition.
- 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_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
| PDg | Predicate description generation | batch_69fe8dde8d008190b03dc0f97618073c |
completed | May 9, 2026, 1:29 a.m. |
Created at: May 1, 2026, 1:58 a.m.