Triple
T30062361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chengjiang County |
E763923
|
entity |
| Predicate | hasNearbyPaleontologicalSite |
P52075
|
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, hasNearbyPaleontologicalSite, Chengjiang Fossil Site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyPaleontologicalSite Context triple: [Chengjiang County, hasNearbyPaleontologicalSite, Chengjiang Fossil Site]
-
A.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
B.
hasNotableFossilSite
Indicates that an entity contains or is associated with a fossil site recognized as significant or noteworthy.
-
C.
discoveredAsFossilSite
Indicates that a location was identified and recognized as a site containing fossils.
-
D.
nearGeologicalSite
chosen
Indicates that one entity is located in close physical proximity to a geological site or feature.
-
E.
hasDinosaurMuseum
Indicates that a place or entity possesses or hosts a museum dedicated primarily to dinosaurs.
- 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_69fe87b609888190913b0c3f787ecdba |
completed | May 9, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69fe8731af48819092084f6f74bf052d |
completed | May 9, 2026, 1 a.m. |
Created at: April 29, 2026, 6:58 p.m.