Triple
T30584187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakusandha Buddha |
E778459
|
entity |
| Predicate | lifespanTraditional |
P585
|
FINISHED |
| Object | 40,000 years |
—
|
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: 40,000 years | Statement: [Kakusandha Buddha, lifespanTraditional, 40,000 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifespanTraditional Context triple: [Kakusandha Buddha, lifespanTraditional, 40,000 years]
-
A.
lifespan
chosen
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
B.
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.
-
C.
lifePeriod
Indicates the span of time during which an entity exists, is active, or is valid.
-
D.
traditionallyLivedTo
Indicates that an entity customarily or historically resided in a particular place or environment over an extended period.
-
E.
leafLongevity
Indicates the duration for which a leaf remains alive and functional before it senesces or is shed.
- 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_69f224a04b248190b0ca443ec86207b8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68945093481909c6eba86bc50870e |
completed | May 2, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:23 p.m.