Triple
T2658992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Dawson |
E54680
|
entity |
| Predicate | rescuesContext |
P41241
|
FINISHED |
| Object | prevents Rose from jumping off the ship |
—
|
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: prevents Rose from jumping off the ship | Statement: [Jack Dawson, rescuesContext, prevents Rose from jumping off the ship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rescuesContext Context triple: [Jack Dawson, rescuesContext, prevents Rose from jumping off the ship]
-
A.
allegedRescueEvent
Indicates that an event is claimed or reported to be a rescue, but its occurrence or nature is not confirmed as factual.
-
B.
rescuedLocation
Indicates the place where a rescue action occurred or from which someone or something was rescued.
-
C.
rescuedBy
Indicates that one entity has been saved or brought out of danger by another entity.
-
D.
conservationContext
Indicates the conservation-related circumstances or status under which an entity exists, such as its protection level, threats, or management conditions.
-
E.
hasReliefEffortFrom
Indicates that a party receives assistance or support through a relief effort provided by another party.
- 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_69ab49e028948190b97e01d73548b1d9 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd94dcaa48190aec625f68ce61a02 |
completed | March 7, 2026, 7:52 a.m. |
| PD | Predicate disambiguation | batch_69abd81768748190bd965f367cf6ef37 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8dd05c48190b4f90031642c4091 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:53 p.m.