Triple
T32335114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landessynode |
E826149
|
entity |
| Predicate | istOrganVon |
P51318
|
FINISHED |
| Object | öffentlich-rechtlicher Religionsgemeinschaft |
—
|
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: öffentlich-rechtlicher Religionsgemeinschaft | Statement: [Landessynode, istOrganVon, öffentlich-rechtlicher Religionsgemeinschaft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: istOrganVon Context triple: [Landessynode, istOrganVon, öffentlich-rechtlicher Religionsgemeinschaft]
-
A.
numberOfOrgans
Indicates the total count of organs associated with a given entity.
-
B.
mainOrganOf
Indicates that one entity is the primary or central organ responsible for the core functions of another entity (such as an organism or system).
-
C.
tipoDeÓrgano
Indicates that one entity is classified as a specific type or category of organ in relation to another entity.
-
D.
organType
chosen
Indicates that one entity is classified as a specific type or category of organ in relation to another entity.
-
E.
имеетОрган
Indicates that one entity possesses or contains a specific organ as a part of its body.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be1779cc8190abe386c03d31d385 |
completed | May 3, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69f6b633e0c88190a727bb7d2751e2d5 |
completed | May 3, 2026, 2:43 a.m. |
Created at: May 1, 2026, 12:48 a.m.