Triple
T9314533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Environmental Information Regulations 2004 |
E224084
|
entity |
| Predicate | exceptionType |
P28876
|
FINISHED |
| Object | manifestly unreasonable requests |
—
|
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: manifestly unreasonable requests | Statement: [Environmental Information Regulations 2004, exceptionType, manifestly unreasonable requests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exceptionType Context triple: [Environmental Information Regulations 2004, exceptionType, manifestly unreasonable requests]
-
A.
exception
Indicates that a particular case does not follow the usual rule, pattern, or condition that applies to others.
-
B.
errorType
Indicates the specific category or kind of error associated with an event, action, or entity.
-
C.
throws
Indicates that one entity propels or hurls another entity or object through space, typically by a deliberate physical action.
-
D.
reasonForException
chosen
Indicates the specific cause or justification for why a normal rule, process, or condition does not apply in a given case.
-
E.
typeOfFaulting
Indicates the kind or classification of geological faulting that characterizes the relationship between rock units or structures.
- 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.