Triple
T35906550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Lechitic |
E1038486
|
entity |
| Predicate | hasNotableExtinctMember |
P72582
|
FINISHED |
| Object | Slovincian language |
E2157938
|
NE 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: Slovincian language | Statement: [Southern Lechitic, hasNotableExtinctMember, Slovincian language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableExtinctMember Context triple: [Southern Lechitic, hasNotableExtinctMember, Slovincian language]
-
A.
hasExtinctMembers
Indicates that at least some members of the referenced group, class, or category are no longer living or existing.
-
B.
notableExtinctMember
chosen
Indicates that an extinct individual or species is a particularly significant or well-known member of a larger group or category.
-
C.
hasExtinctSubspecies
Indicates that an entity has at least one subspecies that is extinct.
-
D.
hasExtinctSpecies
Indicates that at least one species associated with the subject entity is no longer extant (i.e., has gone extinct).
-
E.
hasExtinction
Indicates that an entity has undergone, is subject to, or is associated with an extinction event or state of no longer existing.
- F. None of above.
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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38dded296c8190825beac69fde1445 |
completed | June 22, 2026, 7:02 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.