Triple
T30656658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mistaken Point Ecological Reserve |
E780403
|
entity |
| Predicate | fossilAssemblageName |
P58140
|
FINISHED |
| Object | Mistaken Point biota |
—
|
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: Mistaken Point biota | Statement: [Mistaken Point Ecological Reserve, fossilAssemblageName, Mistaken Point biota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fossilAssemblageName Context triple: [Mistaken Point Ecological Reserve, fossilAssemblageName, Mistaken Point biota]
-
A.
fossilTypeLocality
Indicates the specific locality that serves as the reference site where the defining fossil specimen(s) of a particular fossil type were originally found.
-
B.
fossilGroup
chosen
Indicates that one entity is classified as belonging to a particular fossil group or assemblage associated with another entity.
-
C.
fossilSiteType
Indicates the specific type or classification of a site where fossils are found or collected.
-
D.
discoveredAsFossilSite
Indicates that a location was identified and recognized as a site containing fossils.
-
E.
fossilDistribution
Indicates the geographic or stratigraphic locations where fossils of an organism or taxon have been found.
- 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_69f224a5d2b481908a6853cd0138e2d7 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68a9c4400819089846344e2e0c547 |
completed | May 2, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:30 p.m.