Triple
T10516798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. John Rivers |
E248054
|
entity |
| Predicate | proposesMarriageAs |
P94333
|
FINISHED |
| Object | duty rather than love |
—
|
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: duty rather than love | Statement: [St. John Rivers, proposesMarriageAs, duty rather than love]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: proposesMarriageAs Context triple: [St. John Rivers, proposesMarriageAs, duty rather than love]
-
A.
acceptsMarriageTo
Indicates that one entity formally agrees to enter into a marriage with another entity.
-
B.
refusedMarriageProposalFrom
Indicates that one entity declined or rejected a marriage proposal made by another entity.
-
C.
engagedTo
Indicates that two entities are formally committed to marry each other.
-
D.
attemptedMarriage
Indicates that one entity tried or intended to enter into a marital relationship with another entity, regardless of whether the marriage was completed or legally recognized.
-
E.
choseAsHusband
Indicates that one entity selected another entity to be her husband, typically as a marital partner.
- 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509cc58b081908ef15aa89b396db6 |
completed | April 7, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69d4fb919ea08190bcc1193e2014d437 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:28 p.m.