Triple
T18476780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kali Yuga |
E451453
|
entity |
| Predicate | humanLifespanTrend |
P131795
|
FINISHED |
| Object | progressive decrease |
—
|
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: progressive decrease | Statement: [Kali Yuga, humanLifespanTrend, progressive decrease]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanLifespanTrend Context triple: [Kali Yuga, humanLifespanTrend, progressive decrease]
-
A.
lifespan
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
B.
lifeExpectancyLevel
Indicates the typical or average length of life expected for an entity, often expressed as a comparative or categorical level.
-
C.
lifespanType
Indicates the type or category of lifespan associated with an entity, such as whether it is finite, indefinite, or of a particular defined duration.
-
D.
deathAge
Indicates the age at which an entity dies or is expected to die.
-
E.
lifetimeInGenerations
Indicates the number of successive generations over which something (e.g., an effect, trait, or validity) persists or remains applicable.
- 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_69d8d38465a0819099b9b42d2a662ac1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53063c0108190be71247567b5241b |
completed | April 19, 2026, 7:43 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2aa72c8190a40854a7a52081e2 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:35 a.m.