Triple
T482804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lepontic language |
E9806
|
entity |
| Predicate | extinctionType |
P14897
|
FINISHED |
| Object | ancient extinction |
—
|
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: ancient extinction | Statement: [Lepontic language, extinctionType, ancient extinction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extinctionType Context triple: [Lepontic language, extinctionType, ancient extinction]
-
A.
extinctionReason
Indicates the cause or factor responsible for an entity’s extinction.
-
B.
extinctionPeriod
Indicates the time span during which an entity ceases to exist or is considered extinct.
-
C.
extinct
Indicates that the referenced entity no longer exists as a living or active member of its former kind or category.
-
D.
typeSpecies
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a higher-level group (such as a genus).
-
E.
threatenedBy
Indicates that one entity poses a danger or potential harm to 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0b8fe6081909f8ab87bfda6b2d8 |
completed | Feb. 28, 2026, 1:42 p.m. |
| PD | Predicate disambiguation | batch_69a2edf321288190b5d560f75782c2cb |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef4030608190b39852b347a505ca |
completed | Feb. 28, 2026, 1:36 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.