Triple
T2576939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Convention (Germany) |
E56998
|
entity |
| Predicate | convenesFor |
P982
|
FINISHED |
| Object | election of the Federal President |
—
|
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 Federal President | Statement: [Federal Convention (Germany), convenesFor, election of the Federal President]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convenesFor Context triple: [Federal Convention (Germany), convenesFor, election of the Federal President]
-
A.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
B.
convenesAs
Indicates that an entity brings together or assembles a group, body, or session in a particular role or capacity.
-
C.
convenesDuring
Indicates that one entity formally gathers or brings together another entity or group during a specified time period or event.
-
D.
convenesOn
Indicates that an event, group, or body holds a meeting or session at a specific time or date.
-
E.
convenes
chosen
Indicates bringing people or groups together to formally meet, discuss, or deliberate on a particular matter.
- 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_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. |
Created at: March 6, 2026, 9:49 p.m.