Triple
T15238595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coelophysis |
E364193
|
entity |
| Predicate | fossilAbundance |
P87416
|
FINISHED |
| Object | numerous articulated skeletons |
—
|
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: numerous articulated skeletons | Statement: [Coelophysis, fossilAbundance, numerous articulated skeletons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fossilAbundance Context triple: [Coelophysis, fossilAbundance, numerous articulated skeletons]
-
A.
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).
-
B.
fossilsFoundOn
Indicates that fossils are discovered or located on a particular surface, layer, or object.
-
C.
fossilRecordStatus
Indicates the preservation state or condition of an organism’s remains as documented in the fossil record.
-
D.
skeletonAbundance
chosen
Indicates the relative quantity or richness of skeletal remains present in or associated with an entity.
-
E.
fossilGroup
Indicates that one entity is classified as belonging to a particular fossil group or assemblage associated with another entity.
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007da7e988190925a9b67b8070bc7 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.