Triple
T24470224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semigallian |
E617077
|
entity |
| Predicate | extinctionApproximate |
P7427
|
FINISHED |
| Object | late Middle Ages |
—
|
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 Middle Ages | Statement: [Semigallian, extinctionApproximate, late Middle Ages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extinctionApproximate Context triple: [Semigallian, extinctionApproximate, late Middle Ages]
-
A.
extinctionCertainty
Indicates the degree of confidence or likelihood that an entity (typically a species or population) will become extinct.
-
B.
extinctionType
Indicates the specific manner or category by which an entity ceases to exist or becomes extinct.
-
C.
extinctionPeriod
chosen
Indicates the time span during which an entity ceases to exist or is considered extinct.
-
D.
hasExtinction
Indicates that an entity has undergone, is subject to, or is associated with an extinction event or state of no longer existing.
-
E.
extinctionIntensity
Indicates the severity or magnitude of extinction events affecting entities within a given context or time interval.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299432b2881909502f9cbc7e4dbb0 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.