Triple
T35540421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Californian |
E1027043
|
entity |
| Predicate | observedMysteriousShipOnHorizon |
P184647
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [SS Californian, observedMysteriousShipOnHorizon, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedMysteriousShipOnHorizon Context triple: [SS Californian, observedMysteriousShipOnHorizon, true]
-
A.
landSightedBy
Indicates that a particular area of land has been visually observed or detected by a specified observer.
-
B.
visibilityFromShore
Indicates that something can be seen or is visually detectable from the shoreline or coast.
-
C.
shipAtTimeOfDisappearance
Indicates that a particular ship is associated with the specific time at which it disappeared.
-
D.
aboardShip
Indicates that one entity is physically on or inside a ship, typically as a passenger, crew member, or cargo.
-
E.
notableShip
Indicates that there is a notable or significant ship associated with the subject entity.
- 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_69f7b365288c8190bcb11fcfba028737 |
completed | May 3, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
| PDg | Predicate description generation | batch_69f7b2f2b9ac8190aa05b8a1aa18ec2d |
completed | May 3, 2026, 8:41 p.m. |
Created at: May 3, 2026, 4:04 p.m.