Triple
T28826149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Denham |
E727909
|
entity |
| Predicate | attitudeTowardMarriage |
P62195
|
FINISHED |
| Object | highly mercenary |
—
|
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: highly mercenary | Statement: [Lady Denham, attitudeTowardMarriage, highly mercenary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attitudeTowardMarriage Context triple: [Lady Denham, attitudeTowardMarriage, highly mercenary]
-
A.
hasAttitudeTowardMarriage
chosen
Indicates that an entity holds a particular opinion, feeling, or stance regarding the institution or concept of marriage.
-
B.
regardsMarriageAs
Indicates that one entity holds a particular view, attitude, or evaluative stance toward the institution or concept of marriage.
-
C.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
D.
attitudeTowardSpouse
Indicates a person's emotional or evaluative stance toward their spouse within the marital relationship.
-
E.
attitudeTowardSex
Indicates an entity’s stance, feelings, or evaluative position regarding sex or sexual activity.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65938f7f0819092bc35567719cd6e |
completed | May 2, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:36 a.m.