Triple
T14881303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suzanne Simonin |
E350004
|
entity |
| Predicate | hasFamilyConflict |
P61068
|
FINISHED |
| Object | parents forcing convent life |
—
|
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: parents forcing convent life | Statement: [Suzanne Simonin, hasFamilyConflict, parents forcing convent life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFamilyConflict Context triple: [Suzanne Simonin, hasFamilyConflict, parents forcing convent life]
-
A.
notableFamilyConflict
Indicates a significant, recognized dispute or ongoing tension between members of the same family.
-
B.
relationshipConflictWith
Indicates a state of opposition, disagreement, or incompatibility between two entities within a relationship.
-
C.
parentalConflictWith
Indicates a relationship in which two parents are in disagreement, tension, or dispute with each other, often over child-related or family matters.
-
D.
hasFamilySituation
Indicates the familial status or circumstances that apply to an entity, such as their family composition, responsibilities, or living situation.
-
E.
hasCauseOfConflict
chosen
Indicates a relationship where one entity is the source or reason for a conflict involving another entity.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e7c0e48190af2d68a71130585c |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.