Triple
T36719481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Empress of Britain (1982) |
E907009
|
entity |
| Predicate | reflagged |
P113059
|
FINISHED |
| Object | multiple times |
—
|
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: multiple times | Statement: [SS Empress of Britain (1982), reflagged, multiple times]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflagged Context triple: [SS Empress of Britain (1982), reflagged, multiple times]
-
A.
reflaggedAs
chosen
Indicates that an entity has been assigned a new flag, status, or label, replacing or superseding its previous one.
-
B.
refloated
Indicates that something previously afloat but no longer buoyant has been returned to a floating condition, typically by refilling with air or restoring buoyancy.
-
C.
reflightOf
Indicates that one flight is a re-scheduled, repeated, or follow-up instance of another original flight.
-
D.
refit
Indicates that an existing object or structure is being modified, repaired, or equipped with new parts or features to restore or improve its function.
-
E.
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.
- 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_69f76e73ad108190a5241585f2303e9a |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c84319dc8190987c08469720d6b1 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.