Triple
T7709367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Käthe Stresemann |
E174708
|
entity |
| Predicate | social role |
P268
|
FINISHED |
| Object | figure in German political circles |
—
|
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: figure in German political circles | Statement: [Käthe Stresemann, social role, figure in German political circles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: social role Context triple: [Käthe Stresemann, social role, figure in German political circles]
-
A.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
B.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
C.
roleInText
Indicates that an entity participates in a text with a specific function or capacity (e.g., author, editor, character).
-
D.
specialRole
Indicates that an entity holds a distinctive or exceptional function, status, or responsibility in relation to another entity or context.
-
E.
formRole
Indicates that an entity assumes, is assigned, or functions in a particular role within a specified context or structure.
- 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_69c6995b3e8c8190833108f883d5f53c |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702ebb7448190ae8d47fe0cbb0907 |
completed | March 27, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69c701683dec8190be9861e592aa8ce0 |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:04 p.m.