Triple
T22793662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stormberg |
E564181
|
entity |
| Predicate | hasFossilsFrom |
P123156
|
FINISHED |
| Object | Late Triassic |
—
|
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: Late Triassic | Statement: [Stormberg, hasFossilsFrom, Late Triassic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFossilsFrom Context triple: [Stormberg, hasFossilsFrom, Late Triassic]
-
A.
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).
-
B.
containsFossilsFrom
chosen
Indicates that one entity includes or preserves fossil remains originating from another entity.
-
C.
fossilsFoundOn
Indicates that fossils are discovered or located on a particular surface, layer, or object.
-
D.
fossilRich
Indicates that a location, layer, or material contains an abundant or significant concentration of fossils.
-
E.
fossilDiscoverer
Indicates the relationship in which an agent is the one who discovered or unearthed a particular fossil.
- 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cd751f081909c7907c96c9906ea |
completed | April 29, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:30 p.m.