Triple
T28036635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U-Dig Fossils area |
E708425
|
entity |
| Predicate | typicalFossilGenus |
P202185
|
FINISHED |
| Object | Elrathia kingii |
—
|
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: Elrathia kingii | Statement: [U-Dig Fossils area, typicalFossilGenus, Elrathia kingii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFossilGenus Context triple: [U-Dig Fossils area, typicalFossilGenus, Elrathia kingii]
-
A.
fossilRecordType
Indicates the classification of how a fossil is preserved or represented in the geological record (e.g., body fossil, trace fossil, cast, mold).
-
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.
fossilGroup
Indicates that one entity is classified as belonging to a particular fossil group or assemblage associated with another entity.
-
D.
knownFromFossils
Indicates that the existence or occurrence of something is inferred or established based on fossil evidence.
-
E.
fossilsFoundOn
Indicates that fossils are discovered or located on a particular surface, layer, or object.
- F. None of above. chosen
Provenance (4 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_6a005e8a2f7c819085bfc6f04b866d87 |
completed | May 10, 2026, 10:31 a.m. |
| PD | Predicate disambiguation | batch_6a005de82ef08190a015b385d1d3443c |
completed | May 10, 2026, 10:28 a.m. |
| PDg | Predicate description generation | batch_6a005e89803c8190ad732ad15affb81f |
completed | May 10, 2026, 10:31 a.m. |
Created at: April 27, 2026, 8:21 p.m.