Triple
T18803586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gesetz gegen Wettbewerbsbeschränkungen |
E459816
|
entity |
| Predicate | firstEnacted |
P1260
|
FINISHED |
| Object | 1957 |
—
|
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: 1957 | Statement: [Gesetz gegen Wettbewerbsbeschränkungen, firstEnacted, 1957]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEnacted Context triple: [Gesetz gegen Wettbewerbsbeschränkungen, firstEnacted, 1957]
-
A.
initialEnactment
Indicates that an action, rule, or condition is being put into effect for the first time, marking its original enactment or coming into force.
-
B.
firstPromulgatedUnder
Indicates the authority, regime, or leadership under which something (typically a law, policy, or decree) was initially formally issued or enacted.
-
C.
firstStatuteEnactedBy
Indicates that a given statute is the earliest (first) law formally enacted by a specified legislative body or authority.
-
D.
dateEnacted
chosen
Indicates the date on which a law, policy, or formal measure was officially put into effect or became legally operative.
-
E.
dateOfEnactment
Indicates the specific calendar date on which a law, regulation, or formal measure officially comes into force.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a0253f748190998995e3b1524357 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.