Triple
T19317109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Millennium Ecosystem Assessment |
E483127
|
entity |
| Predicate | policyAudience |
P793
|
FINISHED |
| Object | governments |
—
|
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: governments | Statement: [Millennium Ecosystem Assessment, policyAudience, governments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyAudience Context triple: [Millennium Ecosystem Assessment, policyAudience, governments]
-
A.
hasAudiencePolicy
Indicates that there is a specified rule or policy governing which audience or group is allowed to access, view, or receive something.
-
B.
hasAudience
chosen
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
C.
regulatoryAudience
Indicates that something is intended for, directed toward, or relevant to a regulatory body or oversight authority as its audience.
-
D.
audienceAccess
Indicates that one entity has permission or ability to access, view, or engage with a particular audience associated with another entity.
-
E.
relatesToAudience
Indicates a general relationship or relevance between something and a particular audience or group of recipients.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e60d843640819089ff3738aae29eb1 |
completed | April 20, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0ef66881909d489d634eee817a |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:32 p.m.