Triple
T19236305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raton Formation |
E481005
|
entity |
| Predicate | hasTypeOfFossil |
P9689
|
FINISHED |
| Object | terrestrial vertebrates |
—
|
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: terrestrial vertebrates | Statement: [Raton Formation, hasTypeOfFossil, terrestrial vertebrates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfFossil Context triple: [Raton Formation, hasTypeOfFossil, terrestrial vertebrates]
-
A.
hasFossilEvidence
Indicates that there exists fossil-based evidence supporting the existence, occurrence, or characteristics of the related entity or event.
-
B.
containsFossilsOf
chosen
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.
describedAsFossil
Indicates that something is characterized or identified as a fossil.
-
D.
containsFossilsFrom
Indicates that one entity includes or preserves fossil remains originating from another entity.
-
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.
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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faed9ef0819085035cc17d1546e5 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:26 p.m.