Triple
T26864384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gemeindeordnung Baden-Württemberg |
E676423
|
entity |
| Predicate | hatRechtsgebiet |
P94406
|
FINISHED |
| Object | Kommunalrecht |
—
|
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: Kommunalrecht | Statement: [Gemeindeordnung Baden-Württemberg, hatRechtsgebiet, Kommunalrecht]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hatRechtsgebiet Context triple: [Gemeindeordnung Baden-Württemberg, hatRechtsgebiet, Kommunalrecht]
-
A.
gehörtZuRechtsgebiet
chosen
Indicates that something is assigned or belongs to a particular legal field or area of law.
-
B.
heldRight
Indicates that one entity is being held on the right side of another entity.
-
C.
heldForJurisdiction
Indicates that an entity is being detained or kept in custody specifically for legal or jurisdictional reasons by a particular authority.
-
D.
rechtskracht
Indicates that a legal decision, rule, or act has binding legal force and is formally effective and enforceable.
-
E.
affectedJurisdictionOver
Indicates that one entity’s authority, control, or legal power extends over and impacts the jurisdiction of another 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_69eee9ba94bc8190b44c5d4397d04ecd |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61e96d45881909f2b93dfc522064f |
completed | May 2, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:27 a.m.