Triple
T13203448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympic class |
E314296
|
entity |
| Predicate | HMHSBritannicFate |
P72523
|
FINISHED |
| Object | sank in 1916 during World War I |
—
|
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: sank in 1916 during World War I | Statement: [Olympic class, HMHSBritannicFate, sank in 1916 during World War I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HMHSBritannicFate Context triple: [Olympic class, HMHSBritannicFate, sank in 1916 during World War I]
-
A.
RMS SegwunStatus
Indicates the operational or contextual status associated with the RMS Segwun at a given time or in a given situation.
-
B.
sankOnMaidenVoyage
Indicates that the subject vessel sank during its very first voyage.
-
C.
missionAtTimeOfSinking
chosen
Indicates that a vessel was engaged in a specific mission or operational role at the time it sank.
-
D.
legalStatusAtTimeOfSinking
Indicates the legal status or condition that applied to an entity at the specific time it sank.
-
E.
shipsSunkOrTotalLoss
Indicates that the referenced ships were sunk or otherwise rendered a total loss (permanently unusable).
- 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_69d806aee7308190b70a237ba2a6e3e1 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c9961a48190a1157df47f59b7af |
completed | April 10, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69d98bc938f081909f123bdf1263ff7f |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:17 p.m.