Triple
T7594927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Rochester |
E179833
|
entity |
| Predicate | proposalInterruptedBy |
P59504
|
FINISHED |
| Object | Revelation of existing marriage to Bertha Mason |
—
|
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: Revelation of existing marriage to Bertha Mason | Statement: [Mr. Rochester, proposalInterruptedBy, Revelation of existing marriage to Bertha Mason]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposalInterruptedBy Context triple: [Mr. Rochester, proposalInterruptedBy, Revelation of existing marriage to Bertha Mason]
-
A.
wasInterruptedBy
chosen
Indicates that an ongoing event, action, or process was stopped or disrupted by another event, action, or agent.
-
B.
constructionInterruptedBy
Indicates that an ongoing construction process is halted, delayed, or disrupted due to the actions or occurrence of another specified entity or event.
-
C.
preempts
Indicates that one action, decision, or rule takes priority over and prevents the application or effect of another.
-
D.
intervenedIn
Indicates that an entity took action to alter, influence, or interrupt the course of an event, process, or interaction involving other entities.
-
E.
proposalProcess
Indicates the process or sequence of actions involved in creating, submitting, reviewing, and deciding on a proposal between entities.
- 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_69c69f3487ec8190bf7acdf2dd91e6d6 |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9bbcd8081909a229d7faa2ffdc8 |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.