Triple
T11630691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bundestag electoral district |
E276387
|
entity |
| Predicate | canBeRedrawn |
P88292
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Bundestag electoral district, canBeRedrawn, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeRedrawn Context triple: [Bundestag electoral district, canBeRedrawn, yes]
-
A.
canRender
Indicates that one entity has the capability or functionality to generate or display another entity in a visual or presentable form.
-
B.
isPainted
Indicates that one entity has applied paint to cover or decorate the surface of another entity.
-
C.
canBeReconfigured
chosen
Indicates that one entity has the capability to be altered, adjusted, or rearranged into a different configuration, typically under certain conditions or using specific methods.
-
D.
canBeDepictedAs
Indicates that one entity is capable of being visually represented or illustrated in the form or style of another entity.
-
E.
canBeReissued
Indicates that something is eligible to be issued again, such as a document, license, or item that can be re-granted or re-produced after its initial issuance.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a127b2688190ae3a340f851e834b |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:39 p.m.