Triple
T24659247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mukupirnidae |
E610491
|
entity |
| Predicate | fossilRecordType |
P157165
|
FINISHED |
| Object | skeletal remains |
—
|
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: skeletal remains | Statement: [Mukupirnidae, fossilRecordType, skeletal remains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fossilRecordType Context triple: [Mukupirnidae, fossilRecordType, skeletal remains]
-
A.
fossilRecordStatus
Indicates the preservation state or condition of an organism’s remains as documented in the fossil record.
-
B.
fossilSiteType
Indicates the specific type or classification of a site where fossils are found or collected.
-
C.
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.
-
D.
fossilMorphology
Indicates that one entity describes or characterizes the physical form and structural features of a fossil associated with another entity.
-
E.
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).
- 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_69e2c4d453248190a020354e93ef6282 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f422add8508190a76e56cfa756eeb8 |
completed | May 1, 2026, 3:49 a.m. |
Created at: April 18, 2026, 2:34 a.m.