Triple
T5056162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundesversammlung |
E113907
|
entity |
| Predicate | convenesRegularly |
P47991
|
FINISHED |
| Object | four regular sessions per year |
—
|
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: four regular sessions per year | Statement: [Bundesversammlung, convenesRegularly, four regular sessions per year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: convenesRegularly Context triple: [Bundesversammlung, convenesRegularly, four regular sessions per year]
-
A.
convenesIn
Indicates that an entity brings together or assembles a group, meeting, or event at a specific place or venue.
-
B.
meetsRegularly
chosen
Indicates that two or more entities come together on a recurring or scheduled basis.
-
C.
convenesAs
Indicates that an entity brings together or assembles a group, body, or session in a particular role or capacity.
-
D.
convenesDuring
Indicates that one entity formally gathers or brings together another entity or group during a specified time period or event.
-
E.
convenesOn
Indicates that an event, group, or body holds a meeting or session at a specific time or date.
- 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_69bd443aa1f88190abb992d138f2cf42 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd744e45588190beaa2f96bb2f41e2 |
completed | March 20, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69bd715479f08190933604aebd34414f |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:38 p.m.