Triple
T9314514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Environmental Information Regulations 2004 |
E224084
|
entity |
| Predicate | statutoryInstrumentNumber |
P53005
|
FINISHED |
| Object | 2004 No. 3391 |
—
|
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: 2004 No. 3391 | Statement: [Environmental Information Regulations 2004, statutoryInstrumentNumber, 2004 No. 3391]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statutoryInstrumentNumber Context triple: [Environmental Information Regulations 2004, statutoryInstrumentNumber, 2004 No. 3391]
-
A.
statutoryScheme
Indicates that one entity is part of, governed by, or defined within a particular statutory or legislative framework.
-
B.
regulationNumber
chosen
Indicates the specific identifier or code assigned to a regulation that governs or constrains an entity or activity.
-
C.
stateBillNumber
Indicates the specific identifying number assigned to a bill within a particular state legislature.
-
D.
publicLawNumber
Indicates the specific public law identifier associated with a legislative act or statute.
-
E.
statuteApprovedBy
Indicates that a statute has received formal approval or authorization from a specified person, body, or authority.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20b2274481908ddb4eda70cea8cc |
completed | April 1, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.