Triple
T32335110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Landessynode |
E826149
|
entity |
| Predicate | tagtIn |
P173975
|
FINISHED |
| Object | Plenarsitzungen |
—
|
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: Plenarsitzungen | Statement: [Landessynode, tagtIn, Plenarsitzungen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tagtIn Context triple: [Landessynode, tagtIn, Plenarsitzungen]
-
A.
tagType
Indicates the classification or category assigned to a tag, specifying what kind of tag it is or how it should be interpreted.
-
B.
hasTamga
Indicates that an entity bears or is marked with a specific tamga (a distinctive emblem, brand, or clan/ownership mark).
-
C.
hasTagmata
Indicates that an organism possesses distinct functional body regions (tagmata) into which its body is divided.
-
D.
tikanga
Indicates the culturally appropriate, customary, or correct way of doing things within a particular social or cultural context.
-
E.
taluk
Indicates an administrative relationship where an area or settlement belongs to, is governed by, or falls within the jurisdiction of a specific taluk (sub-district).
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:48 a.m.