Triple
T27957394
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landesminister |
E703588
|
entity |
| Predicate | hatRechtsgrundlageIn |
P125
|
FINISHED |
| Object | Landesverfassung |
—
|
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: Landesverfassung | Statement: [Landesminister, hatRechtsgrundlageIn, Landesverfassung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatRechtsgrundlageIn Context triple: [Landesminister, hatRechtsgrundlageIn, Landesverfassung]
-
A.
legalBasis
chosen
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
B.
legalStandingBasis
Indicates the legal grounds or justification on which a party’s standing or authority in a legal matter is based.
-
C.
legalBasisInEU
Indicates that something (such as a measure, decision, or status) is grounded in, justified by, or derived from a specific legal basis within European Union law.
-
D.
legalSystemBasis
Indicates the foundational legal framework, tradition, or set of principles on which a legal system is based.
-
E.
haveLaw
Indicates that a governing body or jurisdiction possesses, enforces, or is characterized by a particular law or set of laws.
- 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_69ef840c8b2c8190946ae9522774ba51 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:29 p.m.