Triple
T30386768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KDE e.V. |
E772972
|
entity |
| Predicate | legalBaseLocatedIn |
P6190
|
FINISHED |
| Object | Berlin |
—
|
NE NERFINISHED |
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: Berlin | Statement: [KDE e.V., legalBaseLocatedIn, Berlin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalBaseLocatedIn Context triple: [KDE e.V., legalBaseLocatedIn, Berlin]
-
A.
legalLicenseJurisdiction
Indicates the legal authority or geographic area under whose laws a particular license is granted, valid, or enforced.
-
B.
legalJurisdiction
chosen
Indicates the legal authority or geographic area whose laws and courts have the power to govern, regulate, or adjudicate matters involving the related entities.
-
C.
legalProtectionJurisdiction
Indicates the jurisdiction or legal authority under which an entity is granted legal protection.
-
D.
localLawRepresentedBy
Indicates that a specific local law is formally represented, expressed, or captured by a particular legal document, code section, or representation.
-
E.
locationOfLawChallenged
Indicates the jurisdiction or place in which a particular law is being contested or legally challenged.
- 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_69f2248ef0a48190aa54d4d8ac3e5758 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: April 29, 2026, 8:01 p.m.