Triple
T38239524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Priestewitz |
E1013719
|
entity |
| Predicate | isSubjectToLegalSystem |
P12605
|
FINISHED |
| Object | German law |
—
|
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: German law | Statement: [Priestewitz, isSubjectToLegalSystem, German law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubjectToLegalSystem Context triple: [Priestewitz, isSubjectToLegalSystem, German law]
-
A.
hasLegalSystemType
Indicates that an entity possesses or is governed by a particular type or form of legal system.
-
B.
usedLegalSystemOf
Indicates that one entity applied, followed, or operated under the legal system or body of laws belonging to another entity.
-
C.
countryOfLegalSystem
Indicates the relationship between a legal system and the country in which that legal system is officially established or applied.
-
D.
legalSystemImposed
Indicates that one authority or group has established and enforced a particular legal system upon another population or territory.
-
E.
governedByLegalRegime
chosen
Indicates that an entity is subject to, regulated by, or operating under a specific legal framework or set of legal rules.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.