Triple
T13780877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DR |
E331126
|
entity |
| Predicate | regulatesContentBy |
P110926
|
FINISHED |
| Object | Danish 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: Danish law | Statement: [DR, regulatesContentBy, Danish law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesContentBy Context triple: [DR, regulatesContentBy, Danish law]
-
A.
regulatesContentFor
Indicates that one entity controls, manages, or sets rules governing the content produced, shared, or accessed by another entity.
-
B.
regulateBy
Indicates that one entity exercises control, guidance, or governance over another entity’s behavior, operation, or state through rules, mechanisms, or constraints.
-
C.
regulatesUse
Indicates that one entity controls, governs, or sets rules for how another entity may be used.
-
D.
regulatesIn
Indicates that one entity controls, modulates, or influences the activity, expression, or behavior of another entity within a system or process.
-
E.
regulatesWith
Indicates that one entity controls, modulates, or influences the activity, state, or behavior of another entity through some regulatory mechanism or interaction.
- F. None of above. chosen
Provenance (4 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02460a688190a27874f8d35819c7 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe97846c819093b00ea117b64e0d |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59db0148190bcaf9646403ca64f |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 10:11 p.m.