Triple
T35540453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Frankfurt |
E1027044
|
entity |
| Predicate | respondedToDistressCallFrom |
P143369
|
FINISHED |
| Object | RMS Titanic |
—
|
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: RMS Titanic | Statement: [SS Frankfurt, respondedToDistressCallFrom, RMS Titanic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: respondedToDistressCallFrom Context triple: [SS Frankfurt, respondedToDistressCallFrom, RMS Titanic]
-
A.
distressSignalSentBy
Indicates that a distress signal is transmitted or initiated by a particular entity.
-
B.
soughtAssistanceFrom
Indicates that one entity actively requested help, support, or guidance from another entity.
-
C.
seeksToRescue
chosen
Indicates an entity’s intention or effort to save or free another entity from danger, harm, or an undesirable situation.
-
D.
rescueOperation
Indicates an action where one entity undertakes efforts to save or free another entity from danger, harm, or a threatening situation.
-
E.
rescueCoordinatedBy
Indicates that a rescue operation is organized, directed, or managed by a particular coordinating entity.
- 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_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.