Triple
T5631821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhynia |
E147849
|
entity |
| Predicate | fossilizationEnvironment |
P40905
|
FINISHED |
| Object | hot-spring influenced wetland |
—
|
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: hot-spring influenced wetland | Statement: [Rhynia, fossilizationEnvironment, hot-spring influenced wetland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fossilizationEnvironment Context triple: [Rhynia, fossilizationEnvironment, hot-spring influenced wetland]
-
A.
depositionalEnvironment
Indicates the natural setting or conditions under which sediments were originally deposited.
-
B.
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).
-
C.
locatedInGeologicPast
Indicates that something existed or occurred in a specific place during a past geologic time period.
-
D.
fossilSiteType
chosen
Indicates the specific type or classification of a site where fossils are found or collected.
-
E.
geologicalFormationProcess
Indicates the natural geological process or set of processes by which a particular geological formation came into existence.
- 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_69c00907bc8881909ed760d3ed73ef35 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0225e8e848190a9ccd48fc0d74e5c |
completed | March 22, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69c01b1f12ec8190b4b9d9ee31cabe19 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:40 p.m.