Triple
T9149144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qijiang District |
E219535
|
entity |
| Predicate | hasDinosaurFossilSite |
P14600
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Qijiang District, hasDinosaurFossilSite, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDinosaurFossilSite Context triple: [Qijiang District, hasDinosaurFossilSite, yes]
-
A.
hasNotableFossilSite
chosen
Indicates that an entity contains or is associated with a fossil site recognized as significant or noteworthy.
-
B.
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).
-
C.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
D.
fossilSiteType
Indicates the specific type or classification of a site where fossils are found or collected.
-
E.
fossilsFoundOn
Indicates that fossils are discovered or located on a particular surface, layer, or object.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca96908d88190a1d12517f6d1aece |
completed | April 1, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.