Triple
T34446210
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artikel 45a Grundgesetz |
E884235
|
entity |
| Predicate | betrifft |
P120650
|
FINISHED |
| Object | Parlamentarische Kontrolle der Streitkräfte |
—
|
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: Parlamentarische Kontrolle der Streitkräfte | Statement: [Artikel 45a Grundgesetz, betrifft, Parlamentarische Kontrolle der Streitkräfte]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: betrifft Context triple: [Artikel 45a Grundgesetz, betrifft, Parlamentarische Kontrolle der Streitkräfte]
-
A.
betreft
chosen
Indicates that something concerns, relates to, or is about something or someone.
-
B.
trägtBeiZu
Indicates that one entity contributes to, promotes, or plays a role in bringing about a certain state, effect, or outcome in another.
-
C.
hatBezugZu
Indicates that one entity has a (often contextual or referential) relation or connection to another entity.
-
D.
unterliegt
Indicates that one entity is subject to, governed or constrained by the authority, rules, influence, or control of another entity.
-
E.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
- 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7194dd0ac819098be37029f4f92d9 |
completed | May 3, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69f71824431081908d9685d2462ea242 |
completed | May 3, 2026, 9:40 a.m. |
Created at: May 1, 2026, 2 a.m.