Triple
T30062334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chengjiang County |
E763923
|
entity |
| Predicate | hasPaleontologicalSignificanceNearby |
P14600
|
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, hasPaleontologicalSignificanceNearby, Chengjiang fossil site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPaleontologicalSignificanceNearby Context triple: [Chengjiang County, hasPaleontologicalSignificanceNearby, Chengjiang fossil site]
-
A.
discoveredAsFossilSite
Indicates that a location was identified and recognized as a site containing fossils.
-
B.
hasNotableFossilSite
chosen
Indicates that an entity contains or is associated with a fossil site recognized as significant or noteworthy.
-
C.
containsFossilsOf
Indicates that one entity (typically a geological formation, rock, or sample) includes fossil remains or traces belonging to another entity (an organism or taxon).
-
D.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
E.
fossilsFoundAt
Indicates that fossil remains of an organism or taxon have been discovered at a particular location or 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_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
Created at: April 29, 2026, 6:58 p.m.