Triple
T32108028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petitions Committee of the Landtag of Brandenburg |
E820037
|
entity |
| Predicate | allowsSubmissionMethod |
P18002
|
FINISHED |
| Object | written petitions |
—
|
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: written petitions | Statement: [Petitions Committee of the Landtag of Brandenburg, allowsSubmissionMethod, written petitions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsSubmissionMethod Context triple: [Petitions Committee of the Landtag of Brandenburg, allowsSubmissionMethod, written petitions]
-
A.
submissionMethod
chosen
Indicates the means or channel through which something is submitted or delivered.
-
B.
approvalMethod
Indicates the method or process by which approval is granted or obtained between entities.
-
C.
hasSubmissionPolicy
Indicates that an entity is associated with a specific set of rules or conditions governing how submissions to it must be made.
-
D.
allowedReturn
Indicates that an entity is permitted to be returned or sent back under specified conditions or rules.
-
E.
mayAllowUse
Indicates that one entity has the potential or permission to allow another entity to use or access something.
- 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_69f3490209c881908ec0241476715f15 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 1, 2026, 12:27 a.m.