Triple
T24534090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Krypton Factor |
E606896
|
entity |
| Predicate | revivalDecade |
P100682
|
FINISHED |
| Object | 2000s |
—
|
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: 2000s | Statement: [The Krypton Factor, revivalDecade, 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revivalDecade Context triple: [The Krypton Factor, revivalDecade, 2000s]
-
A.
revivedInDecade
chosen
Indicates that an entity was brought back into use, popularity, or active existence during a specified decade.
-
B.
restoredInDecade
Indicates that an entity was restored or brought back to a prior or improved condition during a specified decade.
-
C.
decade
Indicates that the relationship or event is associated with, occurs within, or is characteristic of a specific ten-year time period.
-
D.
revivalYear
Indicates the year in which something (such as a work, practice, or institution) was brought back into active use or renewed after a period of decline or inactivity.
-
E.
revivalStars
Indicates a relationship where one entity initiates, leads, or is central to a revival, renewal, or comeback of another entity.
- 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_69e2c4c90c848190b23c4303620dcaaf |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:25 a.m.