Triple
T35540416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Californian |
E1027043
|
entity |
| Predicate | radioOperatorDuringTitanicDisaster |
P109041
|
FINISHED |
| Object | Cyril Evans |
—
|
NE NERFINISHED |
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: Cyril Evans | Statement: [SS Californian, radioOperatorDuringTitanicDisaster, Cyril Evans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: radioOperatorDuringTitanicDisaster Context triple: [SS Californian, radioOperatorDuringTitanicDisaster, Cyril Evans]
-
A.
radioOperator
chosen
Indicates a relationship where one entity serves as the radio operator for another, handling radio communication duties on its behalf.
-
B.
radioDistressChannel
Indicates that an entity is using or associated with a radio channel designated specifically for transmitting distress or emergency communications.
-
C.
radioSystem
Indicates that one entity functions as, or is equipped with, a radio communication system used for transmitting and/or receiving signals.
-
D.
crewCalls
Indicates that a crew member initiates a call or communication to another party.
-
E.
radioEmission
Indicates that one entity emits or produces radio-frequency radiation detectable as radio waves.
- 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_69f76e008ba08190927acd8e5e0344c8 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:04 p.m.