Triple
T30062354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chengjiang County |
E763923
|
entity |
| Predicate | hasBiodiversityNearby |
P22447
|
FINISHED |
| Object | Fuxian Lake |
—
|
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: Fuxian Lake | Statement: [Chengjiang County, hasBiodiversityNearby, Fuxian Lake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBiodiversityNearby Context triple: [Chengjiang County, hasBiodiversityNearby, Fuxian Lake]
-
A.
hasMajorEcosystemNearby
Indicates that one entity is located close enough to another entity that the latter significantly influences or characterizes the surrounding ecosystem.
-
B.
hasBiodiversityFeature
chosen
Indicates that an entity possesses or is associated with a specific biodiversity-related characteristic, attribute, or element.
-
C.
hasNearbyHabitats
Indicates that one entity has other habitats located close to it in geographic or spatial terms.
-
D.
hasNearbyNatureReserve
Indicates that one place or entity is located close to a designated nature reserve.
-
E.
hasBiodiversitySignificance
Indicates that something possesses ecological importance due to the variety, rarity, or conservation value of the species and habitats it supports.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 29, 2026, 6:58 p.m.