Triple
T32964781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gesetzgebung der Evangelisch-Lutherischen Kirche in Bayern |
E843339
|
entity |
| Predicate | createsNormType |
P2826
|
FINISHED |
| Object | Kirchenverfassung |
—
|
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: Kirchenverfassung | Statement: [Gesetzgebung der Evangelisch-Lutherischen Kirche in Bayern, createsNormType, Kirchenverfassung]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createsNormType Context triple: [Gesetzgebung der Evangelisch-Lutherischen Kirche in Bayern, createsNormType, Kirchenverfassung]
-
A.
normType
chosen
Indicates the specific category or classification of a norm that governs or constrains an entity or situation.
-
B.
normalizationType
Indicates the specific method or scheme used to normalize or standardize data, values, or representations within a given context.
-
C.
constructType
Indicates the type or category of construction or structure associated with an entity.
-
D.
hasNorm
Indicates that an entity is associated with, governed by, or characterized through a particular norm, rule, or standard.
-
E.
normIs
Indicates that something conforms to, or is characterized by, a particular standard, rule, or norm.
- 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_69f3494af2808190ad98cec2f1bc0fe6 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fef8c3f2388190b995ec173512945a |
completed | May 9, 2026, 9:05 a.m. |
| PD | Predicate disambiguation | batch_69fef65975608190960b78d27e806d4f |
completed | May 9, 2026, 8:54 a.m. |
Created at: May 1, 2026, 1:21 a.m.