Triple
T34794556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hephzibah Cass |
E1003035
|
entity |
| Predicate | refusesOfferReason |
P6667
|
FINISHED |
| Object | loyalty to Silas Marner |
—
|
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: loyalty to Silas Marner | Statement: [Hephzibah Cass, refusesOfferReason, loyalty to Silas Marner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refusesOfferReason Context triple: [Hephzibah Cass, refusesOfferReason, loyalty to Silas Marner]
-
A.
reasonForReoffer
Indicates the reason or justification for presenting something again after it was previously offered.
-
B.
turnedDownOffer
Indicates that one party rejected or declined an offer made by another party.
-
C.
reasonForDecline
chosen
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
-
D.
refusedMarriageProposalFrom
Indicates that one entity declined or rejected a marriage proposal made by another entity.
-
E.
refusalPhrase
Indicates that an expression conveys a rejection, denial, or unwillingness to accept, agree, or comply.
- 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_69f76db543808190b188c6c86a91491b |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77a83ec9081909309bc3d646f193c |
completed | May 3, 2026, 4:40 p.m. |
| PD | Predicate disambiguation | batch_69f7795b1abc8190823664d1caa94649 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.