Triple
T25296709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khaidi No. 150 |
E634234
|
entity |
| Predicate | marksComebackAfterHiatus |
P61807
|
FINISHED |
| Object | Chiranjeevi |
—
|
NE NERFINISHED |
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: Chiranjeevi | Statement: [Khaidi No. 150, marksComebackAfterHiatus, Chiranjeevi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksComebackAfterHiatus Context triple: [Khaidi No. 150, marksComebackAfterHiatus, Chiranjeevi]
-
A.
releasedAfterHiatusOf
Indicates that one entity (typically a work or product) was released following a preceding break or hiatus of the other entity (such as an artist, series, or organization).
-
B.
madeComeback
Indicates that an entity returned to a previous level of success, performance, or prominence after a period of decline, absence, or setback.
-
C.
comebackContext
Indicates the situational background, circumstances, or prior events that frame or motivate a comeback or return.
-
D.
marksReturnTo
chosen
Indicates a point, event, or condition that signifies the resumption or coming back of something or someone to a prior state, place, or activity.
-
E.
comebackWin
Indicates a victory achieved by overcoming a prior deficit or losing position during the contest or event.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fd2e5ec8190965046138f838057 |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:22 p.m.