Triple
T33264969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beatrice |
E851618
|
entity |
| Predicate | attitudeTowardMarriageAtEnd |
P161039
|
FINISHED |
| Object | accepting |
—
|
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: accepting | Statement: [Beatrice, attitudeTowardMarriageAtEnd, accepting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attitudeTowardMarriageAtEnd Context triple: [Beatrice, attitudeTowardMarriageAtEnd, accepting]
-
A.
hasAttitudeTowardMarriage
Indicates that an entity holds a particular opinion, feeling, or stance regarding the institution or concept of marriage.
-
B.
marriageOutcome
Indicates the result or status that follows from a marriage, such as whether it continues, ends, or changes form.
-
C.
hasMaritalStatusAtEnd
Indicates that an entity possesses a specific marital status at the end of a given period, event, or reference time.
-
D.
regardsMarriageAs
chosen
Indicates that one entity holds a particular view, attitude, or evaluative stance toward the institution or concept of marriage.
-
E.
marriageResolvedBy
Indicates that a marital relationship between two parties has been formally concluded or dissolved through a specific resolving action or process (e.g., divorce, annulment).
- 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_69f349642dac81908a37ffcc3b976a55 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:32 a.m.