Triple
T35540418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Californian |
E1027043
|
entity |
| Predicate | wirelessStatusNightOfTitanicSinking |
P183225
|
FINISHED |
| Object | switched off |
—
|
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: switched off | Statement: [SS Californian, wirelessStatusNightOfTitanicSinking, switched off]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wirelessStatusNightOfTitanicSinking Context triple: [SS Californian, wirelessStatusNightOfTitanicSinking, switched off]
-
A.
Waterline
Indicates the level or line on an object or surface that marks where water reaches or has reached.
-
B.
includesWireless
Indicates that one entity provides or comes equipped with wireless capability, connectivity, or components for another entity.
-
C.
wirelessStandalone
Indicates that something operates wirelessly on its own, without needing to be connected to or dependent on another device or system.
-
D.
wreckDiscoveryAgent
Indicates that an agent discovers or identifies the wreck of something, such as a destroyed vehicle, vessel, or structure.
-
E.
sinkingRecordedOnFilm
Indicates that the act or process of sinking was captured or documented on film.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79a53ccc481908421ae16e69aa8a4 |
completed | May 3, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:04 p.m.