Triple
T29056652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Energy Act 2011 |
E735404
|
entity |
| Predicate | createsScheme |
P4328
|
FINISHED |
| Object | Green Deal |
—
|
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: Green Deal | Statement: [Energy Act 2011, createsScheme, Green Deal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createsScheme Context triple: [Energy Act 2011, createsScheme, Green Deal]
-
A.
catalogueSystemCreator
Indicates that an entity is the creator or originator of a particular catalogue system.
-
B.
creationType
Indicates the manner or process by which something was brought into existence or produced.
-
C.
createdEntityType
Indicates the type or category of entity that was produced or brought into existence as a result of the creation action.
-
D.
createdProgram
Indicates that an entity authored, developed, or produced a particular program (such as software or a coded application).
-
E.
createdRegimeOf
chosen
Indicates that one entity brought about, established, or was responsible for the formation of a particular regime or system of rule for 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
Created at: April 28, 2026, 10:12 a.m.