Triple
T30628432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Schröder cabinet |
E779646
|
entity |
| Predicate | timeInOfficeEra |
P36144
|
FINISHED |
| Object | post-reunification Germany |
—
|
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: post-reunification Germany | Statement: [First Schröder cabinet, timeInOfficeEra, post-reunification Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeInOfficeEra Context triple: [First Schröder cabinet, timeInOfficeEra, post-reunification Germany]
-
A.
timeInOfficeCharacteristic
Indicates a characteristic or attribute specifically related to the duration or period an entity spends in office or in a particular official role.
-
B.
chronologyWithinOffice
Indicates that one event or action occurs within the temporal span of another event or action associated with the same office or term of office.
-
C.
timeInOfficeRelation
chosen
Indicates a temporal relationship specifying the duration or period that an entity holds or held a particular office or position.
-
D.
termInOffice
Indicates the period during which an individual officially holds a particular office or position.
-
E.
notableOfficePeriod
Indicates that an entity held a particular office or position during a specified time period.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:28 p.m.