Triple
T22927421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lepidodendron |
E569345
|
entity |
| Predicate | fossilPart |
P150285
|
FINISHED |
| Object | trunks |
—
|
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: trunks | Statement: [Lepidodendron, fossilPart, trunks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fossilPart Context triple: [Lepidodendron, fossilPart, trunks]
-
A.
fossilTypeMaterial
Indicates that a fossil specimen serves as the designated type material (e.g., holotype, lectotype) for a named taxon.
-
B.
fossilGroup
Indicates that one entity is classified as belonging to a particular fossil group or assemblage associated with another entity.
-
C.
fossilContent
Indicates that one entity contains, preserves, or is characterized by the fossils of another entity.
-
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. 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_69e2458f7d008190901dccbaebeaba24 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180da10648190a67ba113fa8c1370 |
completed | April 29, 2026, 3:54 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:43 p.m.