Triple
T27638220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | environmental law of the European Union |
E696520
|
entity |
| Predicate | supportedByAgency |
P53316
|
FINISHED |
| Object | European Environment Agency |
—
|
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: European Environment Agency | Statement: [environmental law of the European Union, supportedByAgency, European Environment Agency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportedByAgency Context triple: [environmental law of the European Union, supportedByAgency, European Environment Agency]
-
A.
supportAgency
Indicates that one entity provides assistance, backing, or resources to another entity in an official or organizational capacity.
-
B.
usedByAgency
Indicates that something (such as a resource, tool, or service) is utilized or employed by an agency.
-
C.
servesAgency
Indicates that one entity performs services or functions on behalf of, or under the authority of, an agency.
-
D.
hasAgencySupport
chosen
Indicates that an entity receives backing, assistance, or sponsorship from an agency.
-
E.
supervisedAgency
Indicates that one entity oversees, directs, or manages the activities or operations of another agency.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: April 27, 2026, 2:25 p.m.