Triple
T30616698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wiwaxia |
E779333
|
entity |
| Predicate | bodyFossilType |
P157165
|
FINISHED |
| Object | soft-bodied organism |
—
|
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: soft-bodied organism | Statement: [Wiwaxia, bodyFossilType, soft-bodied organism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyFossilType Context triple: [Wiwaxia, bodyFossilType, soft-bodied organism]
-
A.
fossilRecordType
chosen
Indicates the classification of how a fossil is preserved or represented in the geological record (e.g., body fossil, trace fossil, cast, mold).
-
B.
fossilTypeMaterial
Indicates that a fossil specimen serves as the designated type material (e.g., holotype, lectotype) for a named taxon.
-
C.
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).
-
D.
describedAsFossil
Indicates that something is characterized or identified as a fossil.
-
E.
fossilMorphology
Indicates that one entity describes or characterizes the physical form and structural features of a fossil 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_69f224a3307081909a6dca8ca75dbf48 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f689ebcd0c819087ac06e22bd2e51a |
completed | May 2, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69f67e448a9c8190b591374d98799fe3 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:26 p.m.