Triple
T24689990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reuss |
E611406
|
entity |
| Predicate | extinctionOfElderLine |
P110086
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Reuss, extinctionOfElderLine, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extinctionOfElderLine Context triple: [Reuss, extinctionOfElderLine, 20th century]
-
A.
extinctionOfMaleLine
Indicates that a family’s direct male lineage has ended, with no surviving male descendants to continue it.
-
B.
extinctDynasty
chosen
Indicates that a dynasty has ceased to exist and no longer continues through ruling descendants or recognized lineage.
-
C.
hasExtinction
Indicates that an entity has undergone, is subject to, or is associated with an extinction event or state of no longer existing.
-
D.
isRelictLineage
Indicates that an entity represents a surviving remnant of an otherwise extinct evolutionary lineage.
-
E.
extinctUpon
Indicates that one entity ceases to exist or becomes extinct as a direct consequence of, or at the point of, another specified event or condition.
- 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_69e2c4d678b081908910f4271627a31a |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:20 a.m.