Triple
T33489441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Directive (EU) 2019/1024 |
E857698
|
entity |
| Predicate | setsRulesOn |
P8188
|
FINISHED |
| Object | charging for the re-use of public sector information |
—
|
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: charging for the re-use of public sector information | Statement: [Directive (EU) 2019/1024, setsRulesOn, charging for the re-use of public sector information]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setsRulesOn Context triple: [Directive (EU) 2019/1024, setsRulesOn, charging for the re-use of public sector information]
-
A.
setsRulesFor
chosen
Indicates that one entity establishes or defines rules, guidelines, or constraints that another entity is expected to follow.
-
B.
settingOfRule
Indicates the contextual environment, domain, or circumstances within which a particular rule is defined and intended to apply.
-
C.
setsOn
Indicates that one entity places or arranges another entity onto a specified surface, container, or context.
-
D.
usesRulesFrom
Indicates that one entity applies, follows, or is governed by the rules defined or provided by another entity.
-
E.
rulesBy
Indicates that one entity governs, controls, or exercises authoritative power over another entity.
- 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_69f3497547608190a1a0f2365fb713ee |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e564f2a08190bc99090d41429022 |
completed | May 3, 2026, 6:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3db74c081909a991309d835d477 |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:38 a.m.