Triple
T15622512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Addie Bundren |
E375591
|
entity |
| Predicate | relationshipWithAnse |
P119455
|
FINISHED |
| Object | loveless marriage |
—
|
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: loveless marriage | Statement: [Addie Bundren, relationshipWithAnse, loveless marriage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipWithAnse Context triple: [Addie Bundren, relationshipWithAnse, loveless marriage]
-
A.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
B.
relationshipToRelative
Indicates the specific familial connection or kinship role that one person has in relation to a particular relative.
-
C.
relationshipToTracyLord
Indicates the specific type of personal or social relationship an entity has with Tracy Lord.
-
D.
relationshipToFriends
Indicates the type or nature of the relationship an entity has with its friends.
-
E.
relationshipToYoungerFamily
Indicates a familial relationship where one person is related to another who is younger in age within the family.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e9a95f08190b0013ba1428849d3 |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:14 a.m.