Triple
T33827315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Britain (2000) |
E866990
|
entity |
| Predicate | flaggedFor |
P177745
|
FINISHED |
| Object | passenger service |
—
|
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: passenger service | Statement: [SS Empress of Britain (2000), flaggedFor, passenger service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flaggedFor Context triple: [SS Empress of Britain (2000), flaggedFor, passenger service]
-
A.
reflaggedAs
Indicates that an entity has been assigned a new flag, status, or label, replacing or superseding its previous one.
-
B.
flagshipFor
Indicates that one entity serves as the primary or leading representative example for another entity, often embodying its most important qualities or status.
-
C.
flag
Indicates that one entity marks, signals, or draws attention to another entity, often to denote status, importance, or the need for review or action.
-
D.
flagStatus
Indicates the current state or condition assigned to a flag, such as whether it is active, raised, set, or marked in a particular way.
-
E.
formerFlag
Indicates that an entity previously served as a flag of another entity but no longer holds that status.
- 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_69f34991dd248190a659541588506b3c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: May 1, 2026, 1:46 a.m.