Triple
T18602812
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Graptolithina |
E454658
|
entity |
| Predicate | fossilMorphology |
P132753
|
FINISHED |
| Object | saw-blade-like colonies |
—
|
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: saw-blade-like colonies | Statement: [Graptolithina, fossilMorphology, saw-blade-like colonies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fossilMorphology Context triple: [Graptolithina, fossilMorphology, saw-blade-like colonies]
-
A.
fossilGroup
Indicates that one entity is classified as belonging to a particular fossil group or assemblage associated with another entity.
-
B.
limbMorphology
Indicates the structural form, shape, and configuration of an organism’s limbs in relation to its body.
-
C.
fossilDistribution
Indicates the geographic or stratigraphic locations where fossils of an organism or taxon have been found.
-
D.
fossilPreservation
Indicates that a fossil retains evidence of its original features or conditions through specific modes or quality of preservation.
-
E.
fossilTypeMaterial
Indicates that a fossil specimen serves as the designated type material (e.g., holotype, lectotype) for a named 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54751d7ec81909efc4867f649002e |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:45 a.m.