Triple
T1899586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Günter Schabowski |
E37660
|
entity |
| Predicate | afterOccupation |
P1691
|
FINISHED |
| Object | publicist |
—
|
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: publicist | Statement: [Günter Schabowski, afterOccupation, publicist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: afterOccupation Context triple: [Günter Schabowski, afterOccupation, publicist]
-
A.
resumedOccupation
Indicates that an entity has returned to and continued a previous occupation or role after a period of interruption or absence.
-
B.
after
chosen
Indicates that one event, state, or action occurs later in time than another, following it in temporal order.
-
C.
earlierOccupation
Indicates that one occupation held by an entity occurred before another occupation in that entity’s work history.
-
D.
postWarOccupation
Indicates that one entity occupied, administered, or controlled another entity or territory in the period following a war.
-
E.
hadOccupationStatusUntil
Indicates that an entity held a particular occupational status up to, but not necessarily beyond, a specified point in time.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb17181b0819090683c55fd1352cb |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe7e7e88190b58c0df59187c0c2 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.