Triple
T15626092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Environmental Impact Statement |
E375681
|
entity |
| Predicate | isReviewedBy |
P1394
|
FINISHED |
| Object | regulatory authorities |
—
|
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: regulatory authorities | Statement: [Environmental Impact Statement, isReviewedBy, regulatory authorities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isReviewedBy Context triple: [Environmental Impact Statement, isReviewedBy, regulatory authorities]
-
A.
reviewedBy
chosen
Indicates that an item, work, or action has been examined and evaluated by a specific agent or reviewer.
-
B.
reviewedAs
Indicates that one entity has evaluated, critiqued, or assessed another entity in a particular capacity, role, or context.
-
C.
areReviewedEvery
Indicates that one entity conducts reviews of another entity at every specified time interval or on every relevant occasion.
-
D.
reviewableBy
Indicates that an entity is subject to evaluation, inspection, or assessment by a specified agent or party.
-
E.
reviewedFor
Indicates that one entity has examined or evaluated another entity for a specific purpose, standard, or context.
- 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_69d85cd035a48190b73d5579ab73969a |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e9e5e248190ae54cda1fde51efb |
completed | April 16, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69deda868d4481908f4bce1c64d2902a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:14 a.m.