Triple
T30062335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chengjiang County |
E763923
|
entity |
| Predicate | hasGeologicalHeritageNearby |
P179009
|
FINISHED |
| Object | Chengjiang fossil site |
—
|
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: Chengjiang fossil site | Statement: [Chengjiang County, hasGeologicalHeritageNearby, Chengjiang fossil site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGeologicalHeritageNearby Context triple: [Chengjiang County, hasGeologicalHeritageNearby, Chengjiang fossil site]
-
A.
nearGeologicalSite
Indicates that one entity is located in close physical proximity to a geological site or feature.
-
B.
nearbyWorldHeritageSite
Indicates that one entity is located close to, or in the immediate vicinity of, a designated World Heritage Site.
-
C.
hasNearbyPilgrimageSite
Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
-
D.
nearbyHeritageDestinations
chosen
Indicates that one or more heritage destinations are located close to a given reference point or entity in geographic space.
-
E.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
- 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_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 29, 2026, 6:58 p.m.