Triple
T8356692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Late Triassic |
E196698
|
entity |
| Predicate | massExtinctionImpact |
P82270
|
FINISHED |
| Object | severe losses in marine faunas |
—
|
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: severe losses in marine faunas | Statement: [Late Triassic, massExtinctionImpact, severe losses in marine faunas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: massExtinctionImpact Context triple: [Late Triassic, massExtinctionImpact, severe losses in marine faunas]
-
A.
massExtinctionCount
Indicates the number of mass extinction events associated with or affecting a given entity or context.
-
B.
extinctionEvent
Indicates a large-scale occurrence that causes the widespread or complete disappearance of one or more species or higher taxonomic groups.
-
C.
extinctionPeriod
Indicates the time span during which an entity ceases to exist or is considered extinct.
-
D.
extinctionType
Indicates the specific manner or category by which an entity ceases to exist or becomes extinct.
-
E.
extinctSpeciesCount
Indicates the number of species within a given scope that have ceased to exist.
- 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_69ca82f08b348190bfb7881944bbff6f |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb804b57f88190907a4e4e389caf5f |
completed | March 31, 2026, 8:05 a.m. |
| PD | Predicate disambiguation | batch_69cb70ca25548190b0f90c5384e3fb3c |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:59 p.m.