Triple
T23301777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenbelt Act, 2005 |
E590320
|
entity |
| Predicate | regionTypeProtected |
P59959
|
FINISHED |
| Object | rural landscape |
—
|
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: rural landscape | Statement: [Greenbelt Act, 2005, regionTypeProtected, rural landscape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionTypeProtected Context triple: [Greenbelt Act, 2005, regionTypeProtected, rural landscape]
-
A.
sectorProtected
Indicates that a particular sector or area is safeguarded from harm, access, or exploitation by some form of protection or regulation.
-
B.
stateProtected
Indicates that an entity is safeguarded or regulated under the laws, authority, or jurisdiction of a specific state.
-
C.
isProtectedAreaOf
chosen
Indicates that a designated protected area (such as a park or reserve) is established to conserve and manage a specific geographic region or natural feature.
-
D.
protectionType
Indicates the kind or method of protection that is applied to or associated with an entity.
-
E.
protectedBy
Indicates that one entity provides protection, defense, or safeguarding for another entity.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196d37fd08190ad2d199c54324c02 |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:04 p.m.