Triple
T28828979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Furong River scenic area |
E727989
|
entity |
| Predicate | hasLandscapeValue |
P192288
|
FINISHED |
| Object | high aesthetic value |
—
|
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: high aesthetic value | Statement: [Furong River scenic area, hasLandscapeValue, high aesthetic value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandscapeValue Context triple: [Furong River scenic area, hasLandscapeValue, high aesthetic value]
-
A.
hasLandscapeType
Indicates that an entity possesses or is characterized by a particular type or category of landscape.
-
B.
hasLandscapeUse
Indicates that something is used or intended to be used within a landscape or landscaping context.
-
C.
hasLandscapeProtection
Indicates that an area or object is subject to legal or formal measures aimed at preserving its landscape or scenic character.
-
D.
isLandscapeAxisFor
Indicates that one element serves as the primary orienting or reference axis that defines the landscape layout or spatial organization of another element.
-
E.
hasLandscapeUseHistory
Indicates that an entity has an associated record or account of how its landscape has been used or managed over time.
- F. None of above. chosen
Provenance (4 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: April 28, 2026, 6:37 a.m.