Triple
T14457921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shisanling Reservoir |
E358502
|
entity |
| Predicate | isInProtectedScenicArea |
P10759
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Shisanling Reservoir, isInProtectedScenicArea, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInProtectedScenicArea Context triple: [Shisanling Reservoir, isInProtectedScenicArea, true]
-
A.
isScenicArea
Indicates that a location is recognized as a scenic area, typically valued for its natural beauty or visually appealing surroundings.
-
B.
isInProtectedArea
chosen
Indicates that an entity is located within a designated protected or conservation area.
-
C.
hasProtectedAreasNearby
Indicates that an entity is located close to one or more designated protected or conservation areas.
-
D.
isTypeOfProtectedArea
Indicates that one entity is classified as a specific type or category of protected area in relation to another entity.
-
E.
hasProtectedAreaStatus
Indicates that an area is officially designated and managed as a protected area under relevant conservation or legal frameworks.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91aabebc819097eb61b2d81c9a91 |
completed | April 14, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.