Triple
T22809748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Staatsratsvorsitzender |
E564639
|
entity |
| Predicate | hatTitel |
P13335
|
FINISHED |
| Object | Genosse Vorsitzender des Staatsrates (in offizieller Anrede) |
—
|
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: Genosse Vorsitzender des Staatsrates (in offizieller Anrede) | Statement: [Staatsratsvorsitzender, hatTitel, Genosse Vorsitzender des Staatsrates (in offizieller Anrede)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatTitel Context triple: [Staatsratsvorsitzender, hatTitel, Genosse Vorsitzender des Staatsrates (in offizieller Anrede)]
-
A.
hadTitle
chosen
Indicates that an entity held or was assigned a specific title or formal designation.
-
B.
title
Indicates that one entity serves as the formal name or designation of another entity.
-
C.
titleThrough
Indicates a relationship where one entity holds or is identified by a specific title by means of, or via the mediation of, another entity or context.
-
D.
hatTeil
Indicates that something is a part or component of something else.
-
E.
titleVariant
Indicates that one title is an alternative or variant form of another title referring to the same work or 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_69e245823f4c8190ade442cdcc2c224a |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17d5f1f348190a35e87939732c99f |
completed | April 29, 2026, 3:39 a.m. |
| PD | Predicate disambiguation | batch_69eed2cb30f481909566369f515f6eff |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:32 p.m.