Triple
T16214558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Französisch Buchholz |
E393551
|
entity |
| Predicate | appliesMunicipalLaw |
P120344
|
FINISHED |
| Object | Berlin state law |
—
|
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: Berlin state law | Statement: [Französisch Buchholz, appliesMunicipalLaw, Berlin state law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliesMunicipalLaw Context triple: [Französisch Buchholz, appliesMunicipalLaw, Berlin state law]
-
A.
appliesLocalLaw
chosen
Indicates that a legal rule, decision, or authority is governed by and enforced under the laws of a specific local jurisdiction.
-
B.
usesMunicipalGovernmentAct
Indicates that an entity operates under, applies, or is governed by the provisions of a Municipal Government Act.
-
C.
hasLocalOrdinances
Indicates that a governing body or jurisdiction has established and enacted specific local ordinances or regulations.
-
D.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
E.
municipalScope
Indicates that something falls within the authority, jurisdiction, or functional domain of a municipality or local city government.
- 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_69d87f1f5bd08190bd01cac0d5b9d2ef |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e227f393e08190be93400d754f0a2d |
completed | April 17, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69e219e94a448190b73a4e6aa374eb4a |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:03 a.m.