Triple
T5178366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hannah Peace |
E116855
|
entity |
| Predicate | hasAttitudeTowardMarriage |
P62195
|
FINISHED |
| Object | nontraditional |
—
|
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: nontraditional | Statement: [Hannah Peace, hasAttitudeTowardMarriage, nontraditional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAttitudeTowardMarriage Context triple: [Hannah Peace, hasAttitudeTowardMarriage, nontraditional]
-
A.
acceptsMarriageTo
Indicates that one entity formally agrees to enter into a marriage with another entity.
-
B.
hasMarriage
Indicates a marital relationship exists between the two entities, specifying that they are or were legally married to each other.
-
C.
marriageType
Indicates the specific legal or social category of a marriage relationship that exists between two spouses.
-
D.
marital status
Indicates the legal or social state of a person’s marriage-related relationship, such as being single, married, divorced, or widowed.
-
E.
hasNotableMarriage
Indicates a marital relationship involving the subject that is considered significant or noteworthy in some context.
- 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_69bd446140f08190becb93c61158f27f |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7976339481909ece900de22064f2 |
completed | March 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69bd77b529948190b86671ebe43f4734 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd79251b548190918a1eb930e24c22 |
completed | March 20, 2026, 4:43 p.m. |
Created at: March 20, 2026, 1:45 p.m.