Triple
T2576989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundesversammlung |
E56999
|
entity |
| Predicate | convenedFor |
P39907
|
FINISHED |
| Object | election of the President of 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: election of the President of Germany | Statement: [Bundesversammlung, convenedFor, election of the President of Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convenedFor Context triple: [Bundesversammlung, convenedFor, election of the President of Germany]
-
A.
convenedIn
Indicates that an event, meeting, or formal gathering was brought together and held at a specific location.
-
B.
convenedOn
Indicates that an event, meeting, or formal gathering took place or was held on a specific date or time.
-
C.
convenesOn
Indicates that an event, group, or body holds a meeting or session at a specific time or date.
-
D.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
E.
convenesBefore
Indicates that one event or gathering is convened and completed before another specified event or gathering begins.
- F. None of above. chosen
Provenance (4 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a73a508190bf12e889a5d4bbf3 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0ce4dcc8190b17a65abf9bd1bb0 |
completed | March 7, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69abd251b48c8190862c7b39ea1bf8ea |
completed | March 7, 2026, 7:22 a.m. |
Created at: March 6, 2026, 9:49 p.m.