Triple
T33573049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georg Dreyman |
E859953
|
entity |
| Predicate | relationshipConflict |
P61665
|
FINISHED |
| Object | Christa-Maria Sieland |
E861555
|
NE 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: Christa-Maria Sieland | Statement: [Georg Dreyman, relationshipConflict, Christa-Maria Sieland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipConflict Context triple: [Georg Dreyman, relationshipConflict, Christa-Maria Sieland]
-
A.
relationshipConflictWith
chosen
Indicates a state of opposition, disagreement, or incompatibility between two entities within a relationship.
-
B.
addressesConflictWithin
Indicates that one entity deals with, manages, or resolves a conflict that exists inside another entity or within its internal scope.
-
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.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
E.
typicalConflict
Indicates that there is a commonly occurring or characteristic conflict or opposition between the related entities.
- F. None of above.
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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a363c7f5ce4819091c441f123121517 |
completed | June 20, 2026, 7:08 a.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:40 a.m.