Triple
T16793769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabinet Adenauer II |
E408178
|
entity |
| Predicate | legislaturePeriodStart |
P45894
|
FINISHED |
| Object | 1953 |
—
|
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: 1953 | Statement: [Cabinet Adenauer II, legislaturePeriodStart, 1953]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislaturePeriodStart Context triple: [Cabinet Adenauer II, legislaturePeriodStart, 1953]
-
A.
parliamentaryTermStarted
Indicates that a specific parliamentary term has begun for a legislative body or member.
-
B.
legislativePeriod
Indicates the specific legislative term or session during which an action, event, or status is valid or took place.
-
C.
currentLegislatureStartYear
chosen
Indicates the calendar year in which the currently serving legislature (or legislative term) officially began.
-
D.
legislatureStartPresidentOfChamber
Indicates that this person began serving as the president (presiding officer) of a legislative chamber at the start of a specified legislative term.
-
E.
congressBeganOn
Indicates the calendar date on which a particular session or term of a congress officially started.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a8b66c8190b83d8af85d2b23a8 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.